Commit Graph

18 Commits

Author SHA1 Message Date
keramida
f7c03d5c19 Note that a UFS filesystem can have up to 20 active snapshots.
PR:		docs/151104
Submitted by:	Aldis Berjoza <aldis@bsdroot.lv>
MFC after:	3 days
2011-02-15 07:25:54 +00:00
jh
598579df4e - Print the nmount(2) provided error message only when it is set.
- Ensure that the error message is NUL-terminated before printing it.

PR:		bin/147482
MFC after:	2 weeks
2010-10-10 09:24:19 +00:00
uqs
1ab3783e1a mdoc: move CAVEATS, BUGS and SECURITY CONSIDERATIONS sections to the
bottom of the manpages and order them consistently.

GNU groff doesn't care about the ordering, and doesn't even mention
CAVEATS and SECURITY CONSIDERATIONS as common sections and where to put
them.

Found by:	mdocml lint run
Reviewed by:	ru
2010-05-13 12:07:55 +00:00
ru
763b9ae1f8 Switch the default WARNS level for sbin/ to 6.
Submitted by:	Ulrich Spörlein
2009-10-19 16:00:24 +00:00
brueffer
2545ffdaed Fix an xref.
PR:		138833
Submitted by:	Alex Keda <admin@lissyara.su>
MFC after:	3 days
2009-09-17 13:09:08 +00:00
pjd
9d4f8dda8f Initialize iov and iovlen before use.
Reported by:	Lucius Windschuh <lwindschuh@googlemail.com>
2009-06-02 18:30:09 +00:00
pjd
d747431e06 - Move from mount(2) to nmount(2). This should allow to convert MNT_SNAPSHOT
flag from a mount flag to FS-specific flag.
- Simplify usage. Instead of 'mksnap_ffs /mnt/foo /mnt/foo/snap' allow to
  give only one argument: 'mksnap_ffs /mnt/foo/snap'. Old usage is also
  accepted for now.
- Add an example of how to mount a snapshot.
2009-05-29 19:18:41 +00:00
kib
84bb2d707f Note that snapshots may cause a panic on the full UFS filesystem.
Submitted by:	pho
MFC after:	3 days
2008-07-26 13:18:33 +00:00
phk
96f1216abd Make sure we don't pass garbage to the kernel.
The filesystem is named "ufs" not "ffs".
2004-12-08 11:54:50 +00:00
des
cf221c4c0d Style nit in previous commit. 2004-01-27 19:28:13 +00:00
mckusick
38230899d9 Preserve acls option on mounts when taking a snapshot.
Submitted by:	Wiktor Niesiobedzki <freebsd-lists@w.evip.pl>
2004-01-27 18:28:11 +00:00
mckusick
62316cd3c7 Check that the user running mksnap_ffs has permission to create and
remove a snapshot file from the directory in which they have requested
to have it made. If they do not have write permission in the directory
or the directory is sticky and not owned by the user, then they
will not be able to remove the snapshot when they are done with it.
2003-11-04 07:04:01 +00:00
trhodes
96d2efc220 style(9): sort functions. 2003-10-29 21:23:44 +00:00
trhodes
fbda80e754 Properly prototype C function usage().
Sync usage() with the manual page: s/file/snapshot_name/g.
2003-10-29 21:21:09 +00:00
charnier
0f87237d88 Replace a reference to non existant mount_ffs(8) by a reference to mount(8). 2003-09-07 14:11:02 +00:00
ru
8bc4d4bba7 mdoc(7) fixes.
Approved by:	re (blanket)
2003-05-24 19:53:08 +00:00
mckusick
abeee19e64 Close out a possible race where anybody in group operator could
chown an arbitrary file to operator.

Reported by:	Ian Dowse <iedowse@maths.tcd.ie>
Sponsored by:   DARPA & NAI Labs.
2003-03-02 08:07:57 +00:00
mckusick
af2849b505 Add the mksnap_ffs command to the sbin directory. This setuid root
program allows users in the operator group to take filesystem
snapshots. Its first use will be in support of `dump -L'.

Approved by:	Technical Review Board <trb@FreeBSD.org>
Sponsored by:   DARPA & NAI Labs.
2003-03-02 01:50:33 +00:00