Hi David,
On Tue, Sep 20, 2011 at 12:19 AM, David Howells <dhowells@xxxxxxxxxx> wrote:
> Michael Kerrisk <mtk.manpages@xxxxxxxxx> wrote:
>
>> I've written the following patch for AT__NO_AUTOMOUNT, which you added
>> to the kernel a while back. Could you please review and ACK/NAK?
>
> It may be worth mentioning that if a mountpoint is already mounted over, then
> this flag has no effect. It merely prevents further automounting.
Thanks. I added a sentence to say that.
Otherwise the text looks okay?
Cheers,
Michael
diff --git a/man2/fstatat.2 b/man2/fstatat.2
index 2868bfb..23c39dc 100644
--- a/man2/fstatat.2
+++ b/man2/fstatat.2
@@ -22,9 +22,7 @@
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
-.\" FIXME: Linux 2.6.38 added AT_NO_AUTOMOUNT
-.\"
-.TH FSTATAT 2 2010-11-21 "Linux" "Linux Programmer's Manual"
+.TH FSTATAT 2 2011-09-19 "Linux" "Linux Programmer's Manual"
.SH NAME
fstatat \- get file status relative to a directory file descriptor
.SH SYNOPSIS
@@ -91,7 +89,19 @@ is absolute, then
is ignored.
.I flags
-can either be 0, or include the following flag:
+can either be 0, or include one or more of the following flags ORed:
+.TP
+.BR AT_NO_AUTOMOUNT " (since Linux 2.6.38)"
+Don't automount the terminal ("basename") component of
+.I pathname
+if it is a directory that is an automount point.
+This allows the caller to gather attributes of an automount point
+(rather than the location it would mount).
+This flag can be used in tools that scan directories
+to prevent mass-automounting of a directory of automount points.
+The
+.B AT_NO_AUTOMOUNT
+flag has no effect if the mount point has already been mounted over.
.TP
.B AT_SYMLINK_NOFOLLOW
If
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
