I recently upgraded from LPRng 3.6.22 to 3.6.26 due to the CERT
advisory, and I've found one annoying difference. We have two user
machines that funnel jobs to a third server machine; I have
force_localhost set in the printcap.
In 3.6.22 an
lpq -Pcclaser
would first show the (usually) empty local queue, and then show the
remote queue where the jobs end up. In 3.6.26 you only see the local
queue, although
lpq -Pcclaser@server
works.
I reinstalled 3.6.22 on one user machine and the old behaviour returned,
ie the 3.6.22 binaries were able to talk to the 3.6.26 lpd on the server and
get the remote queue listing. So I gather that it's just the 3.6.26 local
lpd that doesn't feel like asking the remote for info about the
destination queue. This does not seem to change if I remove the
force_localhost, ie the local lpq just checks the local queue, but not
the remote.
Is this a new feature (I can't seem to find any reference to it in the
HOWTO, or CHANGES files) and is there some way to recover the old
behaviour?
Thanks,
John Harper
------------------------------------
Academic Computing Coordinator
University of Toronto at Scarborough
[EMAIL PROTECTED]
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
