Date: Thu, 18 Jul 1996 21:46:33 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Cc: markd@Grizzly.COM, bugs@freefall.freebsd.org Subject: Re: kern/1397: can't send to a pipe Message-ID: <199607181946.VAA07250@uriah.heep.sax.de> In-Reply-To: <199607181825.OAA14569@skynet.ctr.columbia.edu> from Bill Paul at "Jul 18, 96 02:25:00 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Bill Paul wrote:
> He didn't mean fstat(1), he meant fstat(2). Look at the sample source
Errm yep.
> In this case, he could replace pipe(2) with socketpair(2) in the
> application, but that doesn't change the fact that fstat(2) is reporting
> a bogus result. I suppose a new type has to be added (S_IPIPE?), but
> a question (in my mind at least) of compatibility with other *BSD systems.
BUGS
Applying fstat() to a socket (and thus to a pipe) returns a zeroed
buffer, except for the blocksize field, and a unique device and inode
number.
So there's a bug in the BUGS section in that the st_mode field is also
being set. Anyway, nobody could rely on it...
;-)
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607181946.VAA07250>