Changeset 2385 for pykota/trunk/conf

Show
Ignore:
Timestamp:
07/25/05 19:13:11 (19 years ago)
Author:
jerome
Message:

Added two new directives :

unknown_billingcode : defines what to do when printing if the billing code

used is not present in the database.

overwrite_jobticket : defines a command to launch when overwriting the username

or the billing code used is desirable (for example when
an user interaction should take place, see the work
of George Farris)

Severity : no support for this in the backend right now, so be patient (again).

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • pykota/trunk/conf/pykota.conf.sample

    r2355 r2385  
    307307# If both are defined, the printer option has priority. 
    308308# striptitle : smbprn.?????? 
     309 
     310# Should we launch a command to overwrite the job's ticket ? 
     311# This allows a command to overwrite the username and/or the 
     312# billing code used. 
     313# If unset no command is launched and the job's username and 
     314# billing code are used as they are received. 
     315# If set, the command is launched. 
     316# To overwrite the job's ticket, the command has to print 
     317# on its standard output one or more of the following lines, 
     318# without any prefix or space character : 
     319# 
     320#    USERNAME=the_username_we_want_to_overwrite_with 
     321#    BILLINGCODE=the_billingcode_we_want_to_overwrite_with 
     322# 
     323# NB : the output is entirely read, and the latest value 
     324# seen is used, so you command can output several usernames 
     325# or billing codes and only the latest ones will be used. 
     326# If only USERNAME= lines are printed, the billing code, 
     327# if any, is used unchanged. 
     328# If only BILLINGCODE= lines are printed, the username is 
     329# used unchanged. 
     330# 
     331# This value can be set either globally or on a per printer basis 
     332# If both are defined, the printer option has priority. 
     333# 
     334# overwrite_jobticket : /path/to/some/script/or/command 
     335 
     336# What should we do when we print and the billing code used is 
     337# not present in the database ? 
     338# The default value is 'create' which adds the billing code to the 
     339# database. 
     340# Other values can be : 
     341#       deny 
     342#     which silently rejects the job. 
     343# or : 
     344#       deny(your script here) 
     345#     if you put the path to a script or command here, it is executed, for 
     346#     example you can open a popup window explaining why the job was 
     347#     rejected. 
     348# 
     349# This value can be set either globally or on a per printer basis 
     350# If both are defined, the printer option has priority. 
     351# 
     352# unknown_billingcode : create 
    309353 
    310354# What is the accounting backend to use