| 673 | | |
| | 673 | # Should we ensure that the printer really is idle before |
| | 674 | # sending the job's datas to it ? |
| | 675 | # |
| | 676 | # This directive is only used when you use an internal |
| | 677 | #�hardware accounting mechanism, like hardware(snmp) or |
| | 678 | # hardware(pjl), and is not used for external hardware |
| | 679 | # accounting mechanisms or for software or ink accounting. |
| | 680 | # |
| | 681 | # If PyKota and CUPS are properly configured, i.e. a single |
| | 682 | # computer (the print server) can access to a particular physical |
| | 683 | # printer, or all CUPS+PyKota print servers which access to the |
| | 684 | # same physical printer share a common network directory used |
| | 685 | # by PyKota to lock this printer resource, then it is not necessary |
| | 686 | # to really ensure the printer is idle before the job, because |
| | 687 | # this is already the case : we already wait at the end of the |
| | 688 | # preceding job for the printer to be idle before reading its |
| | 689 | # internal page counter. So setting this value to Yes usually |
| | 690 | # saves a lot of time between jobs, generally around 30 seconds. |
| | 691 | # |
| | 692 | # If you're not sure, leave this value to the default which is No, |
| | 693 | # meaning that before sending the job's datas to the printer, PyKota |
| | 694 | # will ensure this printer is in idle state. |
| | 695 | # |
| | 696 | # If not defined, a value of No is assumed. |
| | 697 | # |
| | 698 | # This value can be set either globally or on a per printer basis |
| | 699 | # If both are defined, the printer option has priority. |
| | 700 | # |
| | 701 | # Sane default : |
| | 702 | # |
| | 703 | skipinitialwait : no |
