> From [EMAIL PROTECTED] Fri Jun 30 13:28:06 2000
> Date: Fri, 30 Jun 2000 15:09:26 -0400
> From: "William R. Knox" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: LPRng: Question and interesting observation (bug?)
>
> First the question -
>
> We are upgrading from LPRng 3.6.5 to LPRng 3.6.19, and are interested in
> maintaining the 'check_idle' functionality that was available
> previously. When I run checkpc on a queue that has this attribute, it
> tells me that I should use the new 'chooser' option instead. However, I
> am not doing load balance queues or printer pools - I merely don't want
> to try and send the job unless I have confirmed that the printer is
> there. Is there any solution to this? Simply dropping 'chooser' into
> place instead of 'check_idle' doesn't seem to have done it.
>
> Now for the interesting behavior. I have the following printcap entry
> for an IP printer on host my_host:
>
> queue_name|QUEUE_NAME:sh:lpd_bounce:tc=.tc_entry:if=/usr/local/etc/filters/ifhp
> -Tmodel=crlfonly:of=/usr/local/bin/lpf:[EMAIL PROTECTED]
>
> The .tc_entry looks like this:
> .tc_entry:\
> sd=/var/spool/lpd/%P:\
> check_idle=/usr/local/eprint/bin/poll_printer.pl -P %P:\
> connect_grace=10:\
> network_connect_grace=10
>
> Under LPRng 3.6.5, this worked fine. lpq would report back as follows:
> Printer: queue_name@my_host (dest [EMAIL PROTECTED]) 'QUEUE_NAME'
> Queue: no printable jobs in queue
> Filter_status: done at 11:36:41.069
> no entries
>
Once again the 'client' and 'server' printcap entries strike.
The LPRng clients simply need 'where to connect' information,
so their printcap entries have the form:
queue_name|QUEUE_NAME:lp=remote_queue@remote_host
OR
queue_name|QUEUE_NAME:rm=remote_host
This will cause the lpq/lpr/lprm/lpc clients to connect to remote_host
and get status from the server on remote_host... UNLESS the 'force_localhost'
flag is set, in which case they will connect to localhost. This was done
due to the large (over 600 as I recall) messages from new LPRng users
that they could not connect to their servers.
Now you also need printcap information for the lpd server. You
tag this with the :server flag. So the 'unexpurgated' printcap
that would cause all clients to connect to the server, regardless of
what the default value of the 'force_localhost' flag is, would be:
# for client
queue_name|QUEUE_NAME:rp=server:force_localhost@
# for server
queue_name|QUEUE_NAME:server
:sh:lpd_bounce:tc=.tc_entry:if=/usr/local/etc/filters/ifhp -Tmodel=crlfonly
:of=/usr/local/bin/lpf:[EMAIL PROTECTED]
.tc_entry
:sd=/var/spool/lpd/%P
:check_idle=/usr/local/eprint/bin/poll_printer.pl -P %P
:connect_grace=10:network_connect_grace=10
Patrick Powell Astart Technologies,
[EMAIL PROTECTED] 9475 Chesapeake Drive, Suite D,
Network and System San Diego, CA 92123
Consulting 858-874-6543 FAX 858-279-8424
LPRng - Print Spooler (http://www.astart.com)
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
