"Anthony Thyssen" said:
> 
> Under LPRng lpq is very versitle in its output
> 
>     lpq -s        a single line
>     lpq           4 header lines and the queue
>     lpq -l        two or three lines for "Status and Filter_Status:
>     lpq -ll       more lines for eact section
>     lpq -lll      even more lines for eact section
>     lpq -L        The complete huge long and verbose status history
> 
> Is there some way of just telling lprng to just NEVER serve the short
> status, WITHOUT destroying the ability to get a longer status?
> 
> For example....
> The option
>    reverse_lpq_status=*
> makes a lprng request  lpq -s the very LONG status report! Arrggghh!!!
> but also makes evrry other lpq option  (-l, -ll and -L) return just
> the useless short status
> 
> The other option
>    force_lpq_status=l=*
> 
> Seems to only effect a "lpq -s" request..  GOOD
> BUT it also returns that very LONG status report!
> I would prefer it to report a "lpq -l" or even a "lpq -ll" report
> instead.  the former being what I would have expected the above option
> to do.
> 
> Peter, can this be fixed, so they don't se that LOOONNNGGGG report!
> and it only affests short: lpq requests.
> 
> Current version of lprng is the latest 3.8.15
> 
> PPS: The  "force_lpq_status" was actully added, due a request by me,
> years ago.  I was having a problem with PC's using "winlpr" and only
> seeing a short status return, presumably because it was designed with
> sun4 lpd in mind when it was written.  I ended up sticking with
> the "reverse_lpq_status" at that time, and making "lpq" on our unix
> boxes a "lpq -s" shell script. ;-)


  Okay, I can now get reverse_lpq_status to work, and it's easiest if I
  use force_lpq_status=l.  The problem, however, is like what you say
  above, except that my SysV clients are getting a "lpq -ll" rather
  than "lpq -L" (if I don't set force_lpq, I get lpq -L as described
  above).  I tried sneaking something past it like using
  force_lpq_status=ln0 but that didn't work.  Theoretically, since it's
  force_lpq_status=l, shouldn't the clients be getting "lpq -l"?

--nate


> 
> 
>   Anthony Thyssen ( System Programmer )    http://www.sct.gu.edu.au/~anthony/
>  -----------------------------------------------------------------------------
>           Like a kite Cut from the string,
>           Lightly the soul of my youth Has taken flight.
>                                                  - Ishikawa Takuboku
>  -----------------------------------------------------------------------------
>      Anthony's Home is his Castle     http://www.sct.gu.edu.au/~anthony/
> 
> -----------------------------------------------------------------------------
> 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.
> -----------------------------------------------------------------------------
> 


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