public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: adas@sourceware.org To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com Subject: Cluster Project branch, master, updated. gfs-kernel_0_1_22-157-gd2d49ff Date: Fri, 11 Apr 2008 14:41:00 -0000 [thread overview] Message-ID: <20080411144137.24290.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Cluster Project". http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=d2d49ff4c65cb6c7912c20a4a55b1d7e60cd3a85 The branch, master has been updated via d2d49ff4c65cb6c7912c20a4a55b1d7e60cd3a85 (commit) from d2a926d2122c23e6175a62326b5e2b421b842a93 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit d2d49ff4c65cb6c7912c20a4a55b1d7e60cd3a85 Author: Abhijith Das <adas@redhat.com> Date: Fri Apr 11 09:40:41 2008 -0500 gfs2_tool manpage: Updates to the manpage for bz441636 ----------------------------------------------------------------------- Summary of changes: gfs2/man/gfs2_tool.8 | 10 +++------- 1 files changed, 3 insertions(+), 7 deletions(-) diff --git a/gfs2/man/gfs2_tool.8 b/gfs2/man/gfs2_tool.8 index 36b90b7..503cddb 100644 --- a/gfs2/man/gfs2_tool.8 +++ b/gfs2/man/gfs2_tool.8 @@ -97,10 +97,9 @@ client when you do this. No one should have to use this. Print out the superblock. .TP \fBsetflag\fP \fIFlag\fR \fIFile1\fR \fIFile2\fR \fI...\fR -Set an attribute flag on a file. There are six currently -supported flags. They are jdata, directio, immutable, appendonly, -noatime, and sync. In most cases, the chattr command may be used -rather than gfs2_tool to set attributes. +Set an attribute flag on a file. The currently supported flags are +jdata, immutable, appendonly, noatime, and sync. In most cases, the +chattr command may be used rather than gfs2_tool to set attributes. The \fIjdata\fR flag causes all the data written to a file to be journaled. If the \fIjdata\fR flag is set for a directory, @@ -108,9 +107,6 @@ all files and directories subsequently created within that directory are also journaled. This behavior replaces the old \fIinherit_jdata\fR flag from gfs. Same as chattr +j. -The \fIdirectio\fR flag causes all I/O to a regular file to be Direct -I/O, even if the O_DIRECT flag isn't used on the open() command. - The \fIimmutable\fR flag marks the file immutable. The behavior is similar to the immutable flag in the ext2/3 filesystems. All write access is denied. Same as chattr +i. hooks/post-receive -- Cluster Project
reply other threads:[~2008-04-11 14:41 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080411144137.24290.qmail@sourceware.org \ --to=adas@sourceware.org \ --cc=cluster-cvs@sources.redhat.com \ --cc=cluster-devel@redhat.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).