Re: LPRng: Page count

2001-01-05 Thread Hermann Lauer

On Thu, Jan 04, 2001 at 01:47:06PM -0500, Brandon S. Allbery KF8NH wrote:
 On Thursday, January 04, 2001 12:24:24 PM -0500, Kenneth Tindle 
 [EMAIL PROTECTED] wrote:
 +-
 | It seems to me that "forewarned is forearmed"- knowing that jobs can
 | be encapsulated, you simply write your parser to deal with that fact
 | from the beginning.  If the printer can interpret the data, then a
 | sufficiently intelligent parsing program should be able to do the same.
 | Did I miss something important?
 +---8
 
 There's the minor issue that determining the true page count of random 
 PostScript documents involves solving the Halting Problem
 
 The evil thing about PostScript is that it is a full programming language. 
 Generally one has to resort to trusting DSC comments or counting instances 
 of "showpage", both of which can be tricked fairly easily.  One can get 
 trickier but there's always another way to defeat it (e.g. if you run a job 
 through Ghostscript to get the page count, not only does it take longer to 
 print but it's also possible to write PostScript code which generates 1 
 page from Ghostscript and 200 on a real printer).
 
 The LPRng HOWTO says it best:  printer accounting is a lost cause.

Really ? I think the ifhp approach (sending a separate ps get pagecount job before
printing, the print the user code and then again send the ps get pagecount
job) is rather save. How can that be fooled ? (without cracking the
printer and things like that nicely described in the HOWTO ...)
And with ps inside pjl the accounting sitiation is even better,
or ?

My original question was rather a convience approach for the user: Give
them the information of the ps output, if he use a wellformed ps file,
he would see his pages (from his large job) printing, if he uses a
bad ps file, he well get nothing or wrong information - not my problem !

Greetings

  Hermann

-- 
Bildverarbeitungsgruppe des Interdiziplinaeren Zentrums fuer
wissenschaftliches Rechnen, Universitaet Heidelberg
INF 368; 69120 Heidelberg; Tel: (06221)54-8826, -6314  Fax: -8850
Email: [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.
-



LPRng: Another behavior change - thppbbt.

2001-01-05 Thread Garry Zacheiss

Under LPRng 3.6.1, sending a short status request (REQ_SHORT in
lpd's terms) would return both the spooling and printing status of the
queue as well as the message set for that queue.  At some point, that
behavior was broken such that only LONG and VERBOSE requests would
return this information; a SHORT request will return the message set for
a given queue and not its printing/spooling state.

This seems broken, and here's a patch against LPRng 3.7.4 that
reverts to the previous behavior.

Garry

--- lpd_status.c.1  Fri Jan  5 10:51:09 2001
+++ lpd_status.cFri Jan  5 10:51:42 2001
@@ -8,7 +8,7 @@
  ***/
 
  static char *const _id =
-"$Id: lpd_status.c,v 1.1 2001/01/05 15:49:31 zacheiss Exp $";
+"$Id: lpd_status.c,v 1.2 2001/01/05 15:51:41 zacheiss Exp $";
 
 
 #include "lp.h"
@@ -777,7 +777,7 @@
Pr_disabled(Spool_control)?"yes":"no",
Pr_aborted(Spool_control)?"yes":"no",
Sp_disabled(Spool_control)?"yes":"no");
-   } else if( displayformat == REQ_DLONG ){
+   } else if( displayformat == REQ_DLONG || displayformat == REQ_DSHORT){
flag = 0;
if( Pr_disabled(Spool_control) || Sp_disabled(Spool_control) || 
Pr_aborted(Spool_control) ){
SNPRINTF( header+len, sizeof(header)-len) " (" );



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



LPRng: pjl_ready_msg confusion

2001-01-05 Thread Jason L Tibbitts III

In ifhp 3.4.4, set pjl_ready_msg to "Printing: \%s{n} \%s{J}" and
pjl_display_size to 32 for my HP 8100DN.  I figured this would put the
obvious up on the screen, as it does with another host running a different
printer and older (slightly hacked[1]) version of ifhp.  Instead, for the
duration of the job I get just the user name in the display while the job
is printing, then at the end I get the expected string for just a second
before "READY" reappears.

I suppose that RDYMSG is supposed to control what's printed while the
printer is idle, but something (probably the pagecount code) is erasing
this.  But what controls the display while the job is printing?  And how
can I get a message to stay on the screen while the printer is idle?

Thanks!

1) My slightly hacked version puts "Printing: user" while the job is
   printing and "Last Job: user" while the printer is idle.  I did this a
   very long time ago, and that patch doesn't match up with current
   versions.

 - J

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



Re: LPRng: lpc hold printer problems

2001-01-05 Thread phillip . griffith

I think you want to say 'lpc stop myprinter' instead of 'lpc hold 
myprinter'. 

'Start' and 'stop' apply to the entire queue.  'Hold' applies to specific 
job(s) within the queue.

Phillip Griffith  (803) 952-8776
Information Technology Department
Westinghouse Savannah River Company




iddwb [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]


01/04/01 12:32 PM
Please respond to lprng

 
To: [EMAIL PROTECTED]
cc: 
Subject:LPRng: lpc hold printer problems


Using Caldera Openlinux distro -- installed from binary lprng-6.2.62.

When issuing an 
'lpc hold myprinter'

I receive the message that printer@host is updated.  However, jobs still
print when I send them through lpr.  issuing

'lpc status myprinter'

say's the printing and spooling are enabled.  When I do an 'lpc disable
myprinter' -- lpc status properly reports that spooling is
disabled.  Trying to lpr on a disabled printer gives me transfer to host
failed -- which I am assuming to be that since the printer was disabled it
won't even accept jobs to hold.  Thats fine.  However, I thought holding a
printer would do just that -- hold the queue from sending to the printer
untill an 'lpc release myprinter' was issued.

what am I doing wrong?

David Bear
College of Public Programs/ASU


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