LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com> To: Michael Kerrisk <mtk-manpages@gmx.net> Cc: val_henson@linux.interl.com, lkml <linux-kernel@vger.kernel.org> Subject: Re: Documenting MS_RELATIME Date: Sat, 10 Feb 2007 19:54:00 -0500 [thread overview] Message-ID: <20070211005400.GC6849@redhat.com> (raw) In-Reply-To: <45CE0737.6010103@gmx.net> On Sat, Feb 10, 2007 at 09:56:07AM -0800, Michael Kerrisk wrote: > Val, > > I'm just updating the mount(2) man page for MS_RELATIME, and this is the > text I've come up with: > > MS_RELATIME(Since Linux 2.6.20) > When a file on this file system is accessed, only > update the file's last accessed time (atime) if > the current value of atime is less than or equal > to the file's last modified (mtime) or last sta- > tus change time (ctime). This option is useful > for programs, such as mutt(1), that need to know > when a file has been read since it was last modi- > fied. > > This text is based on your comments accompanying the various patches, but > it differs in a respect. Your comments said that the atime would only be > updated if the atime is older than mtime/ctime. However, what the code > actually does is update atime if it is is <= mtime/ctime -- i.e., atime is > older than or *or equal to* mtime/ctime. > > I'm sure that the code implements your intention, but before incorporating > the above text I thought I just better check, since the code differs from > your comment. Can you just confirm that the proposed man page text is okay. Whilst on the subject of RELATIME, is there any good reason why not to make this a default mount option ? Dave -- http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-02-11 0:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-10 17:56 Documenting MS_RELATIME Michael Kerrisk 2007-02-11 0:54 ` Dave Jones [this message] 2007-02-12 6:55 ` Valerie Henson 2007-02-12 15:40 ` Dave Jones 2007-02-12 17:49 ` Jan Engelhardt 2007-02-12 17:55 ` Jörn Engel 2007-02-12 19:53 ` Petri Kaukasoina 2007-02-12 19:57 ` Valerie Henson 2007-02-12 19:42 ` Valerie Henson 2007-02-12 6:53 ` Valerie Henson
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=20070211005400.GC6849@redhat.com \ --to=davej@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mtk-manpages@gmx.net \ --cc=val_henson@linux.interl.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 NNTP newsgroup(s).