Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!pipex!uunet!monoli!csoft!newsserv From: Igor Sviridov <sia@lot.cs.kiev.ua> Subject: Re: "Interactive Unix" and lpd daemon Qs X-Return-Path: lotua!lot.cs.kiev.ua!sia Reply-To: sia-@UA.NET Organization: Communication Systems Research Team, Kiev, Ukraine Date: Sat, 26 Nov 1994 13:26:26 GMT Message-ID: <785856386PCTIN@lot.cs.kiev.ua> Lines: 22 Sender: news-service@monolit.kiev.ua In article <199411211917.NAA24415@wahine.jsc.nasa.gov> wally@wahine.jsc.nasa.gov (Walter B. Kulecz Ph.D.) writes: > In article <AP-yuAdMBh107h@pid.kla.com> you wrote: > > I have the same problem on one of my two BSDI systems. One works fine > the other has jobs queued by lpr just hang. Thing is, if I su root and > kill the lpd process and then start another by typing "lpd" I get and > error message to the console saying something like: no /dev/lp device file > but the job then is correctly sent to the remote printer and removed from > the queue, but the next job hangs and so on. May be you just need to specify separate spool directory in /etc/printcap for your remote printer; after jobs are spooled there is no information (other than directory jobs lay in) to determine where to send it... so if there are two entries with same directories in /etc/printcap jobs go to the first destination (hmm, or may be loop through destinations?). > --wally. -- Igor.