Re: !!!Print Server DOWN!!!

["Adam Williams" <awilliam@xxxxxxxxxxxxx>]

> > My Linux print server has gone down.  I have rebooted and restarted lpd to
no
> > effect.  It accepts jobs,  but attempting to send a job results in -
> >
> > littleboy:~ $lpr -Pmskps ls.ps
> > lpr: connect: No such file or directory
> > jobs queued, but cannot start daemon.
> >
> > NIS, DNS and all other network services work great as usual.  I have
narrowed it
> >  down to the lask of /dev/printer (the socket lpd listens to for moving
around
> > print jobs)
> >
> > if I use touch /dev/printer the message changes to:
> >
> > lpr: connect: Connection refused
> > jobs queued, but cannot start daemon.
> >
> > On other Linux machines /dev/printer looks like:
> > srw-------   1 root     root            0 May 26 07:47 printer
> >
> > How on earth do I create this file,  and why does restarting LPD not fix
it?
> >  I've looked into mknod but it does not create sockets.
>
> A Unix domain socket has to be created by the application that listens
> on it (in this case lpd).
>
> Obvious question: is lpd actually running? lpd creates the socket at
> startup and removes it upon termination. If lpd is running but
> /dev/printer doesn't exist, then something has gone horribly wrong
> with lpd.
>

Hmmm.  A 'ps ax' showd lpd running,  and with one child.  I restarted lpd now
and it runs,  by itself,  and work just fine.  So lpd creates /dev/printer,
 and since it was not I assume it was in some sort of block condition before it
reached that state.  Where can one get detailed info on lpr/lpd,  I haven't
seen any books on them specifically.  Is there any was to crack up the debug
level,  so if this happens again I can hunt down the cause?