Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!ariel.unm.edu!nmsu!opus!eoshaugh From: eoshaugh@nmsu.edu (Erik Oshaughnessy) Newsgroups: comp.sys.next Subject: more on the named-pipe bug Message-ID: Date: 25 Feb 91 22:39:20 GMT Sender: news@NMSU.Edu Distribution: comp.sys.next Organization: NMSU Computer Science Lines: 36 I said: >Reading empty named pipes ( created with /etc/mknod .signature p ) Bill from (burdick@mentor.cc.purdue.edu) said: >>I didn't see the 'p' option documneted in the man pages. Perhaps this >>is because it is unsupported. I forgot to mention that the named pipe resided in a shared filespace, and I made the pipe on a Sun 4/260. Wow. Brainstorm! I don't claim to be a guru on this sort of thing, but it strikes me that the NeXT might not grok whatever the 'p' switch does in SunOS. ( I just read the man page for mknod for SunOS and the p mode does, and I quote.. " In the second form, mknod makes a named pipe (FIFO). " Rebuttles? Flames? Ideas? _____________________________________________________________________________ ~ | Erik O'Shaughnessy |\/\/\/| ~ | Small Systems | | ~ | New Mexico State University | * | ~ ()========= | Las Cruces, NM USA | (x)(x) L_l===== | eoshaugh@dante.nmsu.edu C _) ==== |------------------------------------ | ,___| ==== |"Do not follow the NULL pointer, | / | for that path leads to chaos, /____\ Die Bart! Die! | and madness." - me | \ | ----------------------------------------------------------------------------- Brought to you by Super Global Mega Corp .com