Situation: linux (RH 7.1) server with updated lprng, and a print server that speaks the LPD protocol connected to the network.
When I execute "lpr -P P1@printserver <file>", it goes ok directly to the printserver. But I need some filtering, so I made a printer (with a RH printtool), just a basic printcap entry (rm=printserver:rp=P1:if=...). The LPD's behavior was quite strange. I was using "lpr -Plp <file>", and 1) when I tried it first time, it worked 2) next time it didn't 3) I restarted the whole server, it still didn't work 4) I restarted LPD, and it worked 5) I restarted the server again, LPD again and it didn't work I spent two days experimenting and it sometimes worked and sometimes didn't. The print job always appeared in the queue, went through the filter and than dissappeared. The logfile said that it was succesfully sent to the remote printer, but the printserver reported no activity. I tried running lpd -D10, and saw some messages like "can't fork", but I don't know if this is related to the problem. Then I found out, that when I run LPD as root (normally it runs as "lp" user), it works OK ! Does anybody have any idea what this means ? thanks Tomas Pluskal ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address 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. -----------------------------------------------------------------------------
