Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!europa.clark.net!newsfeed.nacamar.de!news-kar1.dfn.de!news-fra1.dfn.de!news-koe1.dfn.de!main.Germany.EU.net!Dortmund.Germany.EU.net!interface-business.de!usenet From: j@ida.interface-business.de (J Wunsch) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: Printer socket broken Date: 12 May 1997 09:22:12 GMT Organization: interface business GmbH, Dresden Lines: 18 Message-ID: <5l6ng4$1ba@innocence.interface-business.de> References: <5kvrmv$ec5@nyx10.cs.du.edu> Reply-To: joerg_wunsch@interface-business.de (Joerg Wunsch) NNTP-Posting-Host: ida.interface-business.de X-Newsreader: knews 0.9.6 X-Phone: +49-351-31809-14 X-Fax: +49-351-3361187 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:6856 dwatson@nyx10.cs.du.edu (darryl watson) wrote: > I managed to crash my system while > a program was using the printer socket, and when the system came back up, > the socket file was gone. :( Sure. Sockets are an IPC facility (actually, the API to it). As such, they only make sense within the context of an attached process. A local-domain socket without an attached process can only be usefully handled with just one command: rm(1). The socket is supposed to be recreated by the server process once it started again (that's lpd in your case). -- J"org Wunsch Unix support engineer joerg_wunsch@interface-business.de http://www.interface-business.de/~j