From: kaih@khms.westfalen.de (Kai Henningsen)
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch?] truncate and timestamps
Date: 23 May 2003 20:02:00 +0200 [thread overview]
Message-ID: <8mRUVSAXw-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305221726300.19226-100000@home.transmeta.com>
torvalds@transmeta.com (Linus Torvalds) wrote on 22.05.03 in <Pine.LNX.4.44.0305221726300.19226-100000@home.transmeta.com>:
> On Fri, 23 May 2003 Andries.Brouwer@cwi.nl wrote:
> >
> > On the other hand, my question was really a different one:
> > do we want to follow POSIX, also in the silly requirement
> > that truncate only sets mtime when the size changes, while
> > O_TRUNC and ftruncate always set mtime.
>
> Does POSIX really say that? What a crock.
That's why POSIX says no such thing.
What it *does* say is
Upon successful completion, if fildes refers to a regular file, the
ftruncate() function shall mark for update the st_ctime and st_mtime
fields of the file and the S_ISUID and S_ISGID bits of the file mode may
be cleared. If the ftruncate() function is unsuccessful, the file is
unaffected.
See:
http://www.opengroup.org/onlinepubs/007904975/functions/ftruncate.html
Is it really so hard to look it up that we need to spout FUD instead?
MfG Kai
next prev parent reply other threads:[~2003-05-23 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 0:17 [patch?] truncate and timestamps Andries.Brouwer
2003-05-23 0:30 ` Linus Torvalds
2003-05-23 1:17 ` viro
2003-05-23 2:42 ` Andrew Morton
2003-05-23 5:11 ` Trond Myklebust
2003-05-23 5:25 ` Trond Myklebust
2003-05-23 3:14 ` David Schwartz
2003-05-26 23:42 ` Alan Cox
2003-05-27 1:17 ` Andrew Morton
2003-05-23 18:02 ` Kai Henningsen [this message]
2003-05-23 19:07 ` Andries Brouwer
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 19:09 Andries.Brouwer
2003-05-22 23:20 ` Andrew Morton
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=8mRUVSAXw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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