Re: !!!Print Server DOWN!!!

[Glynn Clements <glynn@xxxxxxxxxxxx>]

Adam Williams wrote:

> 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?

lpd logs via syslog, using the `lpr' facility, so adding

	lpr.debug	/var/log/lpr

will log all lpr messages.

Also, you can run a program via `strace' to get details of the system
calls that it is making. In the case of a daemon, you will need to use
`strace -f' to trace the child process after the fork().

In the case of a functioning lpd, you should get (amongst other stuff)
calls similar to the following:

[pid  1339] unlink("/dev/printer" <unfinished ...>
[pid  1339] <... unlink resumed> )      = -1 ENOENT (No such file or directory)

[pid  1339] socket(PF_UNIX, SOCK_STREAM, , 0 <unfinished ...>
[pid  1339] <... socket resumed> )      = 4

[pid  1339] bind(4, {sun_family=AF_UNIX, sun_path="/dev/printer"}, 14 <unfinished ...>
[pid  1339] <... bind resumed> )        = 0

-- 
Glynn Clements <glynn@sensei.co.uk>