Return to BSD News archive
Xref: sserve comp.unix.bsd:13406 comp.unix.pc-clone.32bit:5590 comp.unix.programmer:14948 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!auspex-gw!guy From: guy@Auspex.COM (Guy Harris) Newsgroups: comp.unix.bsd,comp.unix.pc-clone.32bit,comp.unix.programmer Subject: Re: [FreeBSD] how to open ( file, O_SYNC | O_WRONLY ) Message-ID: <19830@auspex-gw.auspex.com> Date: 8 Feb 94 21:59:02 GMT References: <2j418c$2co@mercury.mcs.com> Sender: news@auspex-gw.auspex.com Followup-To: comp.unix.bsd Organization: Auspex Systems, Santa Clara Lines: 18 Nntp-Posting-Host: bootme.auspex.com >It seems that FreeBSD (1.0e) doesn't have O_SYNC (SunOS does :), so I am >basicly stuck trying to open a file as a named pipe. SunOS does (having picked up the idea from SVR3), but that flag has no effect whatsoever on named pipes, so I'm not sure why the lack of O_SYNC causes you to be "stuck". The O_SYNC flag can, for those familiar with "fsync()" but not with O_SYNC, be thought of as a file descriptor flag saying "do an 'fsync()' on this descriptor after every write". One doesn't normally open files as named pipes; one normally opens named pipes as named pipes. If, as what you're saying: >I see that mkfifo(1) exists but is under development. ...seems to imply, FreeBSD 1.0e doesn't yet *implement* named pipes, well, you may be out of luck if you want to *open* a named pipe.