"Anthony Thyssen" said: > > 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.
Yeah, with the Adobe filters we used under BSD printing, it would output the display of the printer, plus some other stuff it deemed useful. IFHP puts out things like 'getting end using 'pjl job/eoj' at 12:26:21.699', which, while it tells you what it's doing, is not very intuitive to the end user. It'd be nice to get at least the printer display, and maybe a per-page count. Or something like what Anthony lists above. The current status line is a bit redundant, because it shows you the same thing as the 'active' job line in the queue. Which reminds me, why is it that when a job jams in the queue due to a printer error, the filter status changes to "See the ifhp man page or the ifhp HOWTO for details at 12:34:52.763"? Old filters used to display the error message (like "TOP OR RIGHT DOOR OPEN"). Thanks, --nate > > > 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. > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
