From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: [PATCH] xfsprogs: add projects(5) and projid(5) manpages
Date: Tue, 24 Feb 2009 08:27:37 -0500 [thread overview]
Message-ID: <20090224132737.GA8161@infradead.org> (raw)
Document the /etc/projects and /etc/projid files in their own manpages
instead of in xfs_quota(8).
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: xfsprogs-dev/man/man5/projid.5
===================================================================
--- /dev/null 1970-01-01 00:00:00.000000000 +0000
+++ xfsprogs-dev/man/man5/projid.5 2009-02-23 21:33:15.289051004 +0100
@@ -0,0 +1,29 @@
+.TH projid 5
+.SH NAME
+projid \- the project name mapping file
+.SH DESCRIPTION
+The
+.I /etc/projid
+file provides a mapping between numeric project identifiers and a
+simple human readable name (similar relationship to the one that
+exists between usernames and uids).
+Its format is simply:
+.nf
+.sp
+.in +5
+# comments are hash-prefixed
+# ...
+cage:10
+logfiles:42
+
+.in -5
+.fi
+.PP
+
+This file is optional, if a project identifier cannot be mapped to
+a name, it will be parsed and displayed as a numeric value.
+
+.SH SEE ALSO
+.BR xfs_quota (8),
+.BR xfsctl (3),
+.BR projects (5).
Index: xfsprogs-dev/man/man8/xfs_quota.8
===================================================================
--- xfsprogs-dev.orig/man/man8/xfs_quota.8 2009-02-23 21:35:34.889050486 +0100
+++ xfsprogs-dev/man/man8/xfs_quota.8 2009-02-23 21:36:25.138929778 +0100
@@ -628,46 +628,6 @@ for
.I /etc/projects
to exist. Note that if projects file exists then it is also used.
-.SH FILE FORMATS
-There are two files involved with the tree quota mechanism, namely
-.I /etc/projects
-and
-.IR /etc/projid .
-The latter is optional.
-The
-.I /etc/projects
-file provides a mapping between numeric project identifiers and those
-directories which are the roots of the quota tree.
-Its format is simply:
-.nf
-.sp
-.in +5
-# comments are hash-prefixed
-# ...
-10:/export/cage
-42:/var/log
-.in -5
-.fi
-.PP
-The
-.I /etc/projid
-file provides a mapping between numeric project identifiers and a
-simple human readable name (similar relationship to the one that
-exists between usernames and uids).
-Its format is simply:
-.nf
-.sp
-.in +5
-# comments are hash-prefixed
-# ...
-cage:10
-logfiles:42
-.in -5
-.fi
-.PP
-This file is optional, if a project identifier cannot be mapped to
-a name, it will be displayed as a number only.
-.PP
.SH EXAMPLES
Enabling quota enforcement on an XFS filesystem (restrict a user
to a set amount of space).
@@ -752,4 +712,6 @@ Mapping of numeric project identifiers t
.SH SEE ALSO
.BR df (1),
.BR mount (1),
-.BR sync (2).
+.BR sync (2),
+.BR projid (5),
+.BR projects (5).
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-02-24 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 13:27 Christoph Hellwig [this message]
2009-03-04 17:32 ` [PATCH] xfsprogs: add projects(5) and projid(5) manpages Christoph Hellwig
2009-03-16 6:34 ` Christoph Hellwig
2009-03-21 4:16 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090224132737.GA8161@infradead.org \
--to=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.