It appears that with LPRng 3.6.20, an lpc reread is killing the server
instead of causing it to merely reread the config file. Doing an lpc -D2
reread on a server produces the following output (thousands of lines at
the beginning removed - I have 920 printers. Patrick, if you want them,
I'll mail them directly):
...
lpd server pid 17459 on print-test.mitre.org, sending SIGHUP
2000-07-11-10:48:58.561 print-test [17480] lpc 1606k: cleanup: signal
No signal, Errorcode 0, exits 0
2000-07-11-10:48:58.562 print-test [17480] lpc 1606k: Get_max_fd:
returning 64
2000-07-11-10:48:58.563 print-test [17480] lpc 1606k: Killchildren: pid
17480, signal Interrupt, count 0
2000-07-11-10:48:58.564 print-test [17480] lpc 1606k: *** Dump_pinfo
Killchildren - after - count 0 ***
2000-07-11-10:48:58.564 print-test [17480] lpc 1606k: *** done ***
2000-07-11-10:48:58.565 print-test [17480] lpc 1606k: cleanup: done,
exit(0)
It appears as though an Interrupt signal is being sent instead of a HUP
signal, which is smoking the server.
--
Bill Knox
Senior Operating Systems Programmer/Analyst
The MITRE Corporation
-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
