linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Zack Brown <zbrown@tumblerings.org>
Cc: "Ata, John" <John.Ata@digitalnet.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: incompatible open modes
Date: Thu, 31 Jul 2003 19:35:58 +0200	[thread overview]
Message-ID: <20030731173558.GA2939@win.tue.nl> (raw)
In-Reply-To: <20030731170345.GJ6693@renegade>

> On Thu, Jul 31, 2003 at 12:09:14PM -0400, Ata, John wrote:

> >    the manpage on "open" states that if a file is opened "O_RDONLY|O_TRUNC",
> >    the O_TRUNC is either ignored or an error is returned.  The 2.4 kernel
> >    appears to cheerfully truncate the file on open.  I wondered which
> >    behavior is actually intended.
> >
> >    O_TRUNC
> >        If the file already exists and is a regular file  and  the open
> >        mode  allows  writing  (i.e.,  is O_RDWR or O_WRONLY) it will be
> >        truncated to length 0.  
> >        Otherwise the effect of O_TRUNC is unspecified.
> >        (On many Linux versions it will be ignored; on other versions
> >        it will return an error.)

This was just recently discussed, and it became clear that the parenthetical
remark only led to confusion. It has been deleted. Instead

       The (undefined) effect of O_RDONLY | O_TRUNC various among
       implementations.  On  many  systems  the  file is actually
       truncated.

has been added.

Andries


  reply	other threads:[~2003-07-31 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6DED202D454D3B4EB7D98A7439218D610C9AB7@vahqex2.gfgsi.com>
2003-07-31 17:03 ` incompatible open modes Zack Brown
2003-07-31 17:35   ` Andries Brouwer [this message]
2003-07-31 18:29 Ata, John
2003-07-31 19:14 ` Richard B. Johnson

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=20030731173558.GA2939@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=John.Ata@digitalnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zbrown@tumblerings.org \
    /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;
as well as URLs for NNTP newsgroup(s).