Adendum: SUMMARY: lpc: connect: No such file or directory

To: alpha-osf-managers@xxxxxxxx
Subject: Adendum: SUMMARY: lpc: connect: No such file or directory
From: "Dan Cambron (Motorola SPS/CST CIM)" <cambron@xxxxxxxxxxxxxxxxx>
Date: Mon, 02 Oct 95 14:20:29 -0700
Cc: cambron@xxxxxxxxxxxxxxxxx

I got an answer from DEC on this.  The behavior I described below is a known 
bug with the V3.2 lpd.  If there are jobs in spool when lpd is restarted, it 
may go nuts and start respawning itself.  They pointed me to, and I ftp'ed, a 
patched version of lpd that's supposed to take care of the problem.  

dan

>
>The reply from everyone was to restart lpd.  I did this and it didn't seem to 
>help.  After a /sbin/init.d/lpd stop and all lpd processes gone, I would start
     
>lpd and find 100's of lpd's running in my process table and /dev/printer not 
>created.  LPD seemed to go on a mad fork binge.  I also had print jobs already
     
>in queues, so I made a wild guess and cleaned out all the queues, and things 
>are working now.  If someone more in the know about this can explain it, I am 
>curious.
>
>Thanks again to all for the quick replies.
>
>dan
>
>>
>>Help.
>>
>>I'm getting the above message when I try and lpc restart all or on any 
>>individual queue I have set up. Looks like:
>>
>>
>># lpc restart hplj2
>>hplj2:
>>        no daemon to abort
>>hplj2:
>>lpc: connect: No such file or directory
>>        couldn't start daemon
>>#
>>
>>This is one of those "it worked Friday" things.  All of the entries in my 
>>printcap point to remote machines, but they go to different machines, and all
     
>>of them respond the same way.  I've never seen this before, and I've got user
    s
>     
>>waiting to print.
>>
>>thanks,
>>dan