Re: problem with page accounting

We've been using pykota for a while, it works moderately well
for the most part.  Since it is run as a filter before the job
is actually printed, it queries the printer for the page count
and calculates the usage for the previous job, so it is one step
behind if you want to look at it that way.  Normally not an issue,
but if you have someone print a job from a client that doesn't go
through the postcript filter, that job is never looked at by pykota,
so the next job that does use pykota can get an erroneous count.

It would be nice if the pykota process for each job could be kept around
to get a page count before and after the job, but doing that would require
modification of cups itself.  I have been thinking of working up a
seperate backend process that might be able to do this, but haven't
actually given it much thought yet.  RealSoonNow.

And another nice thing to have would be a lightweight, stand alone
program that could be put on various clients so that users could check
their quotas.  As it is, it appears that one would need to install a
complete suite of the proper database tools for a command line client
program that communicates with the server.

mjb.