Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!inXS.uu.net!newsflash.concordia.ca!news.nstn.ca!ott.istar!istar.net!n3ott.istar!news.comnet.ca!tomqnx.tomqnx.com!tom From: tom@tomqnx.tomqnx.com (Tom Torrance at home) Newsgroups: comp.unix.bsd.freebsd.misc,comp.dcom.fax Subject: Re: FIFO problem w/HylaFaX Followup-To: comp.unix.bsd.freebsd.misc,comp.dcom.fax Date: 20 Jul 1996 23:39:22 GMT Organization: Comnet Communications Lines: 30 Message-ID: <4srqna$74@executor.comnet.ca> References: <4sicv4$79m@bamboo.verinet.com> <4sl7rl$53o@uriah.heep.sax.de> NNTP-Posting-Host: 205.206.213.106 X-Newsreader: TIN [version 1.2 PL2] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:24101 comp.dcom.fax:15107 J Wunsch (j@uriah.heep.sax.de) wrote: : mike@bamboo.verinet.com (Mike Loseke) wrote: : > tested it prior and after with cu. The FIFO file in /var/spool/fax I had : > to create my self (mkfifo FIFO) because faxq couldn't create it itself. : > If I try to start faxd.recv by hand, I get this in //var/log/messages: : > : > [trunc]faxd.recv[25342]: setsockopt (SO_LINGER): Socket operation on non-socket : > [trunc]faxd.recv[25342]: getsockname: Socket operation on non-socket : That rather looks like the file is not supposed to be a real FIFO, but : a local domain socket instead. You cannot create this one with a : command, since it is only valid for the server that has been creating : the socket node. (Despite of this, it looks very similar to a FIFO.) : So the mere question is which server is supposed to create this : socket. : -- : cheers, J"org The hackers approach. I tarred FIFO. renamed it as req'd then untarred it. Works like a charm. -- tom@tomqnx.com Tom Torrance 27 Dayton Cr., Nepean Ont., Canada K2H 7N8 My opinions are personal, and not those of my employer.