Re: concurrent write(2) calls write bad data to file

Article View: comp.bugs.4bsd

Article #579

#579

From: guy
Date: Thu, 12 Mar 1987 20:48

6 lines
930 bytes

>I presume O_APPEND on open?

Or when the program starts; turning on O_APPEND with "fcntl" does the
same job, and is the only way to do it if you're writing to the
standard output (since you aren't the one who opened it).  Yes,
that's what I meant by "forced-append mode".

Technical Details

Message-ID: <14952@sun.uucp>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!panda!genrad!decvax!decwrl!sun!gorodish!guy

References: <692@rtech.UUCP> <14589@sun.uucp> <2841@sdcsvax.UCSD.EDU>

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!panda!genrad!decvax!decwrl!sun!gorodish!guy
From: guy@gorodish.UUCP
Newsgroups: comp.bugs.4bsd,comp.unix.wizards
Subject: Re: concurrent write(2) calls write bad data to file
Message-ID: <14952@sun.uucp>
Date: Thu, 12-Mar-87 15:48:50 EST
Article-I.D.: sun.14952
Posted: Thu Mar 12 15:48:50 1987
Date-Received: Sat, 14-Mar-87 01:09:41 EST
References: <692@rtech.UUCP> <14589@sun.uucp> <2841@sdcsvax.UCSD.EDU>
Sender: news@sun.uucp
Reply-To: guy@sun.UUCP (Guy Harris)
Organization: Sun Microsystems, Mountain View
Lines: 6

Reply to Parent Message