| 53 | | # the 'postgresql' value is deprecated, use 'pgstorage' instead. |
| | 55 | #################################################################### |
| | 56 | # SQLite3 : comment this section out if you use another backend # |
| | 57 | #################################################################### |
| | 58 | |
| | 59 | #storagebackend : sqlitestorage |
| | 60 | #storagename: /etc/pykota/pykota.db |
| | 61 | |
| | 62 | #################################################################### |
| | 63 | # PostgreSQL : comment this section out if you use another backend # |
| | 64 | #################################################################### |
| 76 | | # Should the database caching mechanism be enabled or not ? |
| 77 | | # If unset, caching is disabled. Possible values Y/N/YES/NO |
| 78 | | # caching mechanism works with both PostgreSQL and OpenLDAP backends |
| 79 | | # but may be really interesting only with OpenLDAP. |
| 80 | | # |
| 81 | | # ACTIVATING CACHE MAY CAUSE PRECISION PROBLEMS IN PRINT ACCOUNTING |
| 82 | | # IF AN USER PRINTS ON SEVERAL PRINTERS AT THE SAME TIME. |
| 83 | | # YOU MAY FIND IT INTERESTING ANYWAY, ESPECIALLY FOR LDAP. |
| 84 | | # |
| 85 | | # FYI, I ALWAYS SET IT TO YES ! |
| 86 | | # |
| 87 | | storagecaching: No |
| 88 | | |
| 89 | | # Should full job history be disabled ? |
| 90 | | # If unset or set to No, full job history is kept in the database. |
| 91 | | # This will be useful in the future when the report generator |
| 92 | | # will be written. |
| 93 | | # Disabling the job history can be useful with heavily loaded |
| 94 | | # LDAP servers, to not make the LDAP tree grow out of control. |
| 95 | | # Disabling the job history with the PostgreSQL backend works too |
| 96 | | # but it's probably less useful than with LDAP. |
| 97 | | disablehistory: No |
| 98 | | |
| | 87 | #################################################################### |
| | 88 | # LDAP : comment this section out if you use another backend # |
| | 89 | #################################################################### |
| | 176 | |
| | 177 | ############################################################# |
| | 178 | # ALL directives below are common to ALL storage backends # |
| | 179 | ############################################################# |
| | 180 | |
| | 181 | # Should the database caching mechanism be enabled or not ? |
| | 182 | # If unset, caching is disabled. Possible values Y/N/YES/NO |
| | 183 | # caching mechanism works with both PostgreSQL and OpenLDAP backends |
| | 184 | # but may be really interesting only with OpenLDAP. |
| | 185 | # |
| | 186 | # ACTIVATING CACHE MAY CAUSE PRECISION PROBLEMS IN PRINT ACCOUNTING |
| | 187 | # IF AN USER PRINTS ON SEVERAL PRINTERS AT THE SAME TIME. |
| | 188 | # YOU MAY FIND IT INTERESTING ANYWAY, ESPECIALLY FOR LDAP. |
| | 189 | # |
| | 190 | # FYI, I ALWAYS SET IT TO YES ! |
| | 191 | # |
| | 192 | storagecaching: No |
| | 193 | |
| | 194 | # Should full job history be disabled ? |
| | 195 | # If unset or set to No, full job history is kept in the database. |
| | 196 | # This will be useful in the future when the report generator |
| | 197 | # will be written. |
| | 198 | # Disabling the job history can be useful with heavily loaded |
| | 199 | # LDAP servers, to not make the LDAP tree grow out of control. |
| | 200 | # Disabling the job history with the PostgreSQL backend works too |
| | 201 | # but it's probably less useful than with LDAP. |
| | 202 | disablehistory: No |
| | 203 | |
