> From [EMAIL PROTECTED] Thu Aug 10 11:27:54 2000
> Date: Thu, 10 Aug 2000 11:22:25 -0600
> From: "William D. Colburn (aka Schlake)" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: LPRng: ifhp and jpegs and toes
>
> 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).
Man, and people complain at me about my 'Swiss Army Knife' applications :0-)
>
> 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! :)
Well, you can tell me what the antiques are. You might be surprised
to find that there are some 'majik options' that support them.
Actually, you can get what you want already, from the pagecount stuff.
Use the following filter entries:
pr:
:ifhp=model=model,... flags to get pagecount
:of=/usr/local/libexec/filters/ifhp
:filter=/usr/local/libexec/filters/ifhp
:af=acct
You will find that in your accounting file you get:
start '-q=nnnn' ....
filestart '-q=nnnn+number_of_header_pages' ....
fileend '-q=nnnn+number_of_header_pages+number_of_job_pages' ....
end '-q=nnnn+number_of_header_pages+number_of_job_pages' ....
You can get the 'nnn' from the 'start' line
You can get the 'nnn+number_of_header_pages' from the FIRST 'filestart' line
You can get the 'nnn+number_of_header_pages+number_of_job_pages' from the 'end' line
You now have: number_of_header_pages and number_of_job_pages
I think this is what you want.
Patrick
Patrick Powell Astart Technologies,
[EMAIL PROTECTED] 9475 Chesapeake Drive, Suite D,
Network and System San Diego, CA 92123
Consulting 858-874-6543 FAX 858-279-8424
LPRng - Print Spooler (http://www.astart.com)
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
