12 | | # It seems that network sockets or some other control specific method is the |
13 | | # best way to query the printers. What I have is a bit (well, more than just |
14 | | # a bit) of a brute forced solution. However, it has been working for us for |
| 12 | # It seems that network sockets or some other control specific method is the |
| 13 | # best way to query the printers. What I have is a bit (well, more than just |
| 14 | # a bit) of a brute forced solution. However, it has been working for us for |
17 | | # I'm not at all happy about the sleep's I have in there. On occasion, there |
18 | | # are missing page counts in the log but since the * next * user to print |
19 | | # gets a good pagecount, the parser (a separate program) finds the |
| 17 | # I'm not at all happy about the sleep's I have in there. On occasion, there |
| 18 | # are missing page counts in the log but since the * next * user to print |
| 19 | # gets a good pagecount, the parser (a separate program) finds the |
21 | | # |
22 | | # If you find a way to improve what I have, please let me know. Note that |
23 | | # when this is invoked from printcap, it's expecting that the data coming it |
24 | | # at stdin is a pre-formatted print job (the Windows machines do that |
| 21 | # |
| 22 | # If you find a way to improve what I have, please let me know. Note that |
| 23 | # when this is invoked from printcap, it's expecting that the data coming it |
| 24 | # at stdin is a pre-formatted print job (the Windows machines do that |