"Nathan Coraor" on wrote...
| "Anthony Thyssen" said:
| >
| > "Nathan Coraor" on wrote...
| > | Theoretically, since it's
| > | force_lpq_status=l, shouldn't the clients be getting "lpq -l"?
| > |
| > That is what I thought. Also it seemed to imply that
| > no matter what type of "lpq" request came in, they would all
| > get a "-l" return. I so I tryed to set it
| > force_lpq_status= ll=*
| > But that just fails completely. Seems only a "s" or an "l" works
| > and it seems to only effect a "lpq -s" request. Not very versitile.
| >
| > The WANT: make a "lpq -s" request equivelent to a "lpq -ll".
|
| lpq -ll seems like way overkill for most of my users. All I really
| need them to know is the status of the printer/job process and the
| queue. Even lpq -l is too much, but I can't get it to give me a
| smaller output. Stuff like the Server pid and Unspooler pid isn't
| really information my users need.
|
| I guess this is something of a feature request?
|
For most users in most situations, yeap you are right, much of the
status information is usless, to users. The single line status however
should be retained.
It sounds to me like lpq needs some re-thinking in LPRng, to make it
more user frendly and printer admin controlable.
All the lpq output styles have their use. Though the fineness of the
lpq -lll.... control is probably a little overkill, beyond 2 or three
'-l's you might as well use '-L'.
Even the ultra short, single line quota, is useful for some printer
monitoring scripts, but then that can get that infor from a lpc status
request, and get it for all the printers in the one request.
I would like to see better use of the single line "status" report by
ifhp filter.
For Example...
For the last seven years, I have been using a "ifhp" like filter
(written in perl, for SunOS BSD lpr system, then converted to LPRng).
This filter put into that single line the current "phase" of the printing
project, without any of the "ifhp"s verbose details.
Opening Network Printer
Preparing Printer
Printing
Waiting For EOJ
Finalising
Mailing User Errors and Quota Usage
If the open was delayed more than a minute or two, the message would
update, every so often, to sometime like...
Opening Network Printer for 20 mins 19sec
So you could see at a glance someting was wrong.
In fact the reason I am on the list now is that I need to replace this
script with "ifhp" as it did the printing in a real "kludgy" way.
But even so its reporting was great, I will miss it.
Anthony Thyssen ( System Programmer ) http://www.sct.gu.edu.au/~anthony/
-----------------------------------------------------------------------------
The Skeleton clicked its teeth in a bizarre rictus that might have
been a smile. How would you know if a skeleton was smiling?
-- Larry Niven and Steve Barnes, ``Barzoom Project'' (Dream Park)
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
