Am Donnerstag, 17. Januar 2002 08:41 schrieb Torsten Rosenberger:
Martin Knipper wrote:
Hallo Martin
CUPS filtering for page count purposes is done through the pstops CUPS filter. Win/Samba clients' jobs don't pass this filter, therefor CUPS can't count and it logs a dummy figure of "1" into the page log for those files.
You may however, with the new CUPS 1.1.12 and Samba 2.2.2, use a new feature (documented in "man cupsaddsmb"): make the CUPS printer drivers downloadable for the Win Clients and install them there. Basically it means, you get an Adobe PostScript driver on the Win Clients, vamped up with a sexy CUPS PPD, which will send *all* files as PostScript to CUPS (regardless for the modell type of the target printer); CUPS will have to figure out how to convert it (just like the jobs from any Unix/Linux CUPS client) and just do it...
CAVEAT: you need enogh CPU power, RAM and spooling space for temporary raster data on the CUPS server (as it is now performing the functions of a "RIP" on behalf of your Windows Clients, which it didn't need to in your previous setup).
Of course you could also install the CUPS-PPDs "manually" on your Win boxen (provided they had an Adobe Generic PS driver installed previously); then you could also use IPP (not Samba) to connect them to CUPS (this needs an IPP client for Windows...)
In any of these cases, pstops is part of the RIP-ing filter chain on CUPS. Your files will be accounted for correctly (unless there is a jam on the printer *after* CUPS has done its duty, and the printer looses data already sent by CUPS. But this is a minor issue...)
Das habe ich gestern auch mal ausprobiert und es hat vom Drucken her auch wunderbar geklappt. Leider hat Cupsin diesem Fall nicht in die PageLog geschrieben. Es wurde nur in /var/log/cups/page_log geschrieben, wenn Daten die raw-queue passieren. Jemand eine Idee für mich ? Gruß Martin