Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!usc!apple!agate!linus!linus!mbunix!dsg From: dsg@mbunix.mitre.org (Goldberg) Newsgroups: comp.unix.questions Subject: Re: What does waiting for lock on /dev/... mean" Message-ID: Date: 12 Dec 90 23:07:17 GMT References: <9518@ncar.ucar.edu> Sender: usenet@linus.mitre.org Organization: The Mitre Corp., Bedford, MA. Lines: 28 In-reply-to: fredrick@acd.ucar.edu's message of 12 Dec 90 21:26:13 GMT > wk1:/ # lpq > waiting for lock on /dev/acdps2 > Rank Owner Job Files Total Size > 1st root 18 /usr/spool/qdaemon/tI8QCGy 8123 bytes > There is only one UNIX computer trying to print to these printers, but > there are PCs and MacIntoshes which are also trying to print. > Does anyone have any insight or know how I can restore the print queues > once we see this? BTW is it related to the rpc.lockd daemon? This is > on a Sun SPARCstation running SUNOS4.1. Any insight or comments would > be appreciated. Thanks in advance. --Tim My bet is that /dev/acdps2 is a hard link to /dev/null, and that there are other such hard links for other printers. The lpd program uses the lock files to prevent subsequently started lpd's from messing up the queue. I believe that if you delete the hard links to /dev/null and just touch those files (ie creating a separate lock for each printer), you will be OK. This worked for ethernet connected Imagen printers. I don't know how it will work for whatever software you are using to talk to the Gator box. #include -- Dave Goldberg UNIX Systems Programmer/Administrator The Mitre Corporation MS B020 Bedford, MA 01730 617-271-2460 Domain: dsg@mbunix.mitre.org UUCP: {your neighborhood}!linus!mbunix!dsg