I've noticed this myself. LPRng's lpd is not exactly forthcoming in
telling you there is a problem. I know lpd -F is good for debugging, but
for normal everyday use you wouldn't run it that way.
Or is it a case of some config file not being setup the wrong way?
It would be nice if lpd did syslog more of its problems.
- Craig
----- Forwarded message from Eric Lammerts <[EMAIL PROTECTED]> -----
When I start lprng and something goes wrong (for instance, something
else is already listening on port 515, or 0 bytes free on /var),
lprng does not print any error message and sends nothing to the
syslog. An strace shows the following:
-----------------------------------------------------------------
open("/dev/null", O_WRONLY) = 1
...
dup2(1, 2) = 2
...
bind(5, {sin_family=AF_INET, sin_port=htons(515), sin_addr=
inet_addr("0.0.0.0")}}, 16) = -1 EADDRINUSE (Address already in
use)
...
write(2, "Fatal error - Another print spoo"..., 74) = 74
-----------------------------------------------------------------
Eric
----- End forwarded message -----
--
Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.eye-net.com.au/ <[EMAIL PROTECTED]>
MIEEE <[EMAIL PROTECTED]> Debian developer <[EMAIL PROTECTED]>
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
