On Thu, 10 Aug 2000, William D. Colburn (aka Schlake) wrote:
> Your answer is almost right. It is overhead, but currently it gets
> lumped in with the rest of the print job. I don't like charging for
> print jobs, but I don't have a choice. I certainly don't want to be
> charging for header pages. What I would prefer is that if the header
> page was a completely seperate job so that it wasn't counted as part of
> the pagecount for the current job. I currently have a work around to
> this problem, but it is ugly. I can make our header page generator log
> a *credit* every time I prints out a header page. That would be icky.
> I feel dirty just for even considering it.
>
> Our old filter, the one I am trying to replace with IFHP, used to
> generate one log line per print out. The filter had one mode for use as
> a header page generator. It used all the command line arguments to
> generate the header page we needed, and interacted with the printer in a
> r/w fashion to check for low toner, no paper, and other insidious errors
> (and sent email to someone to fix the problem), then made a one line log
> entry for the header. If it was run as a regular filter it could
> convert just about anything into postscript, and would also do the
> interactions and notifications. It made appropriate log file entries
> and was able to figure out (and usually do the right thing) if someone
> killed the job, power cycled the printer, sent the postscript
> interpreter into a loop, etc, and generated an appropriate line of
> billing information (plus email describing what happened).
>
> Currently, IFHP seems to run once, processing both the header page and
> the print job, and putting the combined pages into its 4 lines of logging
> information.
How many pages is your header? If it is a constant number of pages for
every job, just subtract that from the page count in your accounting
script....
Andy
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
