75 | | Problem may arise however in batches on successive print jobs |
76 | | by different users when there's no sleep time between two jobs : |
77 | | the used pages may be attributed to incorrect user. This |
78 | | depends on the printer speed and time between jobs. |
79 | | |
80 | | Other querying methods which won't suffer from this problem, |
81 | | but probably from other ones ;-) will be implemented in the |
82 | | future. |
| 75 | Problem may theorically arise in batches of successive print jobs by |
| 76 | different users when there's no sleep time between two jobs : the |
| 77 | used pages may theorically be attributed to an incorrect user in the |
| 78 | case that the printer is asked for its page counter at the beginning |
| 79 | of a new job and before the end of the previous job. This depends on |
| 80 | the printer speed and time between jobs, but so far I've not seen |
| 81 | any problem with moderately used printers. This also depends on CUPS |
| 82 | internal behavior : if CUPS doesn't begin to send a job to a printer |
| 83 | before the previous one is completely printed, then there's no |
| 84 | problem. |
| 85 | |
| 86 | Other querying methods which won't suffer from this possible |
| 87 | problem, but probably from other ones ;-) will be implemented in the |
| 88 | future. |
| 168 | WARNING : In the case you've got a non-postscript printer, chances |
| 169 | are that the *cupsFilter is already filled-in and points |
| 170 | to cupsomatic or such a print filter. In this case please |
| 171 | check if you can switch your printer to PostScript mode |
| 172 | or if there's a way to make it accept PostScript jobs. |
| 173 | If yes then ensure that your workstations uses a PostScript |
| 174 | printer driver, and replace the *cupsFilter line with the |
| 175 | one pointing to the pykota filter. This should work, but |
| 176 | is currently untested. |
| 177 | If your printer really needs the original *cupsFilter line |
| 178 | then you may not be able to use PyKota easily for now. |
| 179 | |