public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: [PATCH] xfstests: update README file to document some recent changes
Date: Mon, 02 Aug 2010 12:51:00 -0500	[thread overview]
Message-ID: <1280771460.2236.68.camel@doink> (raw)

Update the README file to document the new _cat_passwd and
_cat_group functions, and to recommend passing "-n" to
getfacl(1) so it produces numeric output.

Signed-off-by: Alex Elder <aelder@sgi.com>

---
 README |   14 ++++++++++++++
 1 file changed, 14 insertions(+)

Index: b/README
===================================================================
--- a/README
+++ b/README
@@ -160,6 +160,20 @@ Test script environment:
 				  string DATE for deterministic
 				  output
 
+	_cat_passwd,		- dump the content of the password
+	_cat_group		  or group file (both the local file
+				  and the content of the NIS database
+				  if it is likely to be present)
+
+     4. General recommendations, usage conventions, etc.:
+	- When the content of the password or group file is
+	  required, get it using the _cat_passwd and _cat_group
+	  functions, to ensure NIS information is included if NIS
+	  is active.
+	- When calling getfacl in a test, pass the "-n" argument so
+	  that numeric rather than symbolic identifiers are used in
+	  the output.
+
 Verified output:
 
     Each test script has a numerical name, e.g. 007, and an associated


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2010-08-02 17:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 17:51 Alex Elder [this message]
2010-08-30 15:05 ` [PATCH] xfstests: update README file to document some recent changes Alex Elder
2010-08-30 21:43 ` Christoph Hellwig

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=1280771460.2236.68.camel@doink \
    --to=aelder@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox