Changeset 2759 for pykota/trunk/conf/pykota.conf.sample
- Timestamp:
- 02/27/06 19:00:44 (18 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
pykota/trunk/conf/pykota.conf.sample
r2692 r2759 327 327 # When the real CUPS backend fail, should we modify the 328 328 # user's page counters and account balance or not ? 329 # Also should we retry and if yes then how often and how many times ? 329 330 # If you trust your users, set it to "nocharge". 330 331 # If you think they found some mean to kill the real CUPS backend, 331 332 # then set it to "charge". 333 # If your print queues get regularly disabled by CUPS when the printers 334 # are switched off, you might want to set it to "retry:N:S" where 335 # N is the number of times the operation should be retried, and S is 336 # the delay in seconds during which PyKota will sleep before trying again. 337 # If N is 0, PyKota will retry indefinitely each S seconds until the 338 # backend succeeds, so you should use this with caution. If N is 0, 339 # of course neither "charge" nor "nocharge" will be honored. 340 # You can combine "charge" or "nocharge" with "retry:N:S" if you want, 341 # by separating the values with a comma as shown in the examples below. 332 342 # If unset, the default value is "nocharge", meaning that users won't be 333 343 # charged whenever a CUPS backend fails. This is the OPPOSITE … … 335 345 # This value can be set either globally or on a per printer basis 336 346 # If both are defined, the printer option has priority. 347 # onbackenderror : charge,retry:5:60 348 # onbackenderror : retry:0:300 349 # onbackenderror : retry:3:300,nocharge 337 350 # onbackenderror : charge 338 351 onbackenderror : nocharge