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.
What I want ifhp to do is to be able to convert anything into postscript
(I have that working now), to spit out one line of logging information
(preferably in our format) with the pagecount in it, and to know what
banner jobs are to be able to log them specially.
Our filters have been around a long time. They support three printers
which your ifhp doesn't support (though probably for good reason). I
think the filters came after we had the DEC, but before PLP came out.
The change from PLP to LPRng wasn't too painful, but keeping up with a
lot of the recent changes has been painful (which is why I was still
running 3.6.2). If I could get a somewhat stock ifhp to work it would
be a happy-happy-joy-joy day for me. Even happier than the day I found
a way to make LPRng compile without having to 'sed' the source code for
our local configuration! :)
On Tue, Aug 08, 2000 at 03:48:43PM -0700, [EMAIL PROTECTED] wrote:
> > So, um, how would I process the accounting for header pages separately
> > from the rest of the print job? I need header pages to have their own
> > special entry in the logfile.
>
> HUH?
>
> You look in the accounting manual, under the entry 'overhead'.
>
> You turn to the accountant and say 'this is overhead'.
>
> He nods and puts it in as 'overhead'.
>
> Or is this the right answer to the wrong question?
>
> Patrick
>
> -----------------------------------------------------------------------------
> 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.
> -----------------------------------------------------------------------------
--
William Colburn, "Sysprog" <[EMAIL PROTECTED]>
Computer Center, New Mexico Institute of Mining and Technology
http://www.nmt.edu/tcc/ http://www.nmt.edu/~wcolburn
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
