Changeset 1594 for pykota/trunk

Timestamp:

07/07/04 11:00:33 (20 years ago)

Author:

jalet

Message:

Better doc on external policy

Files:

• pykota/trunk/conf/pykota.conf.sample (modified) (3 diffs)

pykota/trunk/conf/pykota.conf.sample

@@ -407 +407 @@
 
 
-# Default policy for inexistant users (e.g. root)
-# either allow or deny or external(some command here)
+# Default policy to apply when either :
+#
+#       - Printer doesn't exist in PyKota's database
+#       - User doesn't exist in PyKota's database
+#       - User has no quota entry for this Printer in PyKota's database
+#
+# Value can be either allow or deny or external(some command here)
+#
 # This value can be set either globally or per printer or both.
 # If both are defined, the printer option has priority.
@@ -418 +424 @@
 # if he is unknown. Example :
 # 
-#       policy: external(/usr/bin/edpykota --add --printer %(printername)s --softlimit 50 --hardlimit 60 %(username)s >/dev/null) 
+#   policy: external(/usr/bin/edpykota --add --printer %(printername)s --softlimit 50 --hardlimit 60 %(username)s >/dev/null) 
 #
 # Of course you can launch any command of your choice with this, e.g. :
 #
-#       policy: external(/usr/local/bin/myadminscript.sh %(username)s >/dev/null)
+#   policy: external(/usr/local/bin/myadminscript.sh %(username)s >/dev/null)
 
 # You can use :
@@ -435 +441 @@
 #        layer (filter or backend)
 #
-# If the user still doesn't exist after external policy command was 
-# launched (the external command didn't add it), or if an error occured
-# during the execution of the external policy command, the job is rejected.
+# If the printer, user, or user quota entry still doesn't exist after 
+# external policy command was launched (the external command didn't add it), 
+# or if an error occured during the execution of the external policy 
+# command, then the job is rejected.
 #
 policy: deny