summaryrefslogtreecommitdiffstats
path: root/sbin/mksnap_ffs
Commit message (Collapse)AuthorAgeFilesLines
* Note that a UFS filesystem can have up to 20 active snapshots.keramida2011-02-151-1/+10
| | | | | | PR: docs/151104 Submitted by: Aldis Berjoza <aldis@bsdroot.lv> MFC after: 3 days
* - Print the nmount(2) provided error message only when it is set.jh2010-10-101-2/+6
| | | | | | | - Ensure that the error message is NUL-terminated before printing it. PR: bin/147482 MFC after: 2 weeks
* mdoc: move CAVEATS, BUGS and SECURITY CONSIDERATIONS sections to theuqs2010-05-131-3/+3
| | | | | | | | | | | 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
* Switch the default WARNS level for sbin/ to 6.ru2009-10-191-0/+1
| | | | Submitted by: Ulrich Spörlein
* Fix an xref.brueffer2009-09-171-1/+1
| | | | | | PR: 138833 Submitted by: Alex Keda <admin@lissyara.su> MFC after: 3 days
* Initialize iov and iovlen before use.pjd2009-06-021-0/+2
| | | | Reported by: Lucius Windschuh <lwindschuh@googlemail.com>
* - Move from mount(2) to nmount(2). This should allow to convert MNT_SNAPSHOTpjd2009-05-293-40/+54
| | | | | | | | 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.
* Note that snapshots may cause a panic on the full UFS filesystem.kib2008-07-261-0/+3
| | | | | Submitted by: pho MFC after: 3 days
* Make sure we don't pass garbage to the kernel.phk2004-12-081-1/+2
| | | | The filesystem is named "ufs" not "ffs".
* Style nit in previous commit.des2004-01-271-1/+1
|
* Preserve acls option on mounts when taking a snapshot.mckusick2004-01-271-1/+5
| | | | Submitted by: Wiktor Niesiobedzki <freebsd-lists@w.evip.pl>
* Check that the user running mksnap_ffs has permission to create andmckusick2003-11-041-1/+33
| | | | | | | 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.
* style(9): sort functions.trhodes2003-10-291-8/+8
|
* Properly prototype C function usage().trhodes2003-10-291-1/+3
| | | | Sync usage() with the manual page: s/file/snapshot_name/g.
* Replace a reference to non existant mount_ffs(8) by a reference to mount(8).charnier2003-09-071-1/+1
|
* mdoc(7) fixes.ru2003-05-241-9/+9
| | | | Approved by: re (blanket)
* Close out a possible race where anybody in group operator couldmckusick2003-03-021-2/+11
| | | | | | | chown an arbitrary file to operator. Reported by: Ian Dowse <iedowse@maths.tcd.ie> Sponsored by: DARPA & NAI Labs.
* Add the mksnap_ffs command to the sbin directory. This setuid rootmckusick2003-03-023-0/+171
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.
OpenPOWER on IntegriCloud