Hi,

I'm experiencing a problem running LPRng-3.8.10 under RH Linux 7.1
when trying to use perl programs either to provide printcap
information or acting as a filter.  This worked OK under 3.7.4.  What
happens is that the program seems to hang when attempting to read data
from STDIN. In standalone testing the programs work OK, it's only when
using them with LPRng that the problem arises.

I rewrote the printcap query program so that it would accept the
printer name from -P rather than on STDIN.  However, for the filter
program this option isn't available to me.

Here's the relevant bit of the program:

print STDERR "**** about to read from STDIN\n";
read STDIN, $magic, 80;
print STDERR "**** finished reading from STDIN\n";

... and here's the bit from the status file:

IF filter 'psif' filter msg - '**** about to read from STDIN' at 
2002-04-23-11:06:30.159 ## A=toby@host1+545 number=545 process=20547
waiting for subserver to exit at 2002-04-23-13:13:52.310 ## A=<NULL> number=0 
process=21774

... and it hangs indefinitely here (with additional 'waiting for
subserver to exit' messages very 10 minutes).

However, if I go back to using LPRng-3.7.4 and don't change anything
at all, this all works perfectly.

Thanks for any help
Toby

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

Reply via email to