Hello,

I have recently upgraded our production LPRng from 3.6.19 to 3.6.24 and 
noticed a change of behavior. In 3.6.19, whenever I was issuing an lpq on a 
bounce queue, the request would propagate to the next lpd, showing me the 
queue status of both the local queue and the remote one. In 3.6.24, I only 
receive the status of the local queue. If I stop lpd and start the 3.6.19 
lpd, lpq again returns a "recursive status", so it seems as if the change 
was in the way lpd implements a status request. Is that an intended change 
or an "oops..."? Is there any way to make lpd issue again a "recursive 
status"?

Thanks.
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.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.
-----------------------------------------------------------------------------

Reply via email to