Changeset 1757 for pykota/trunk/conf
- Timestamp:
- 09/29/04 22:20:52 (20 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
pykota/trunk/conf/pykota.conf.sample
r1746 r1757 186 186 # Some people reported that WinXP sends mixed case usernames 187 187 # setting 'utolower: Yes' solves the problem. 188 # Of course you have to use rlowercase only when adding188 # Of course you have to use lowercase only when adding 189 189 # users with edpykota, because ALL database accesses are 190 190 # still case sensitive. … … 192 192 # If utolower is Yes, the usernames received from the printing 193 193 # system is converted to lowercase at the start of the cupspykota 194 # backend or of the pykota filter.194 # backend or of the lprngpykota filter. 195 195 # 196 196 # If utolower is No, which is the default, strict case checking … … 198 198 # different. Printer and groups names are ALWAYS case sensitive. 199 199 utolower: No 200 201 # Should we split usernames on a specific separator when printing ? 202 # Default is No, i.e. if the value is unset. 203 # This is a global option only. 204 # This option adds support for Samba's Winbind utility, which 205 # prefixes usernames with domain name and separator character. 206 # Of course if you set this then you have to use NO separator when 207 # adding users with edpykota. 208 # 209 # If winbind_separator is set, the usernames received from the printing 210 # system are split on the separator's value, and only the last part 211 # (real username) is used. 212 # 213 # If winbind_separator is not set, which is the default, strict 214 # username equality checking will be done (modulo the setting 215 # of the 'utolower' directive), this means that users 'DOMAIN1/jerome', 216 # 'Domain2/jerome' and 'jerome' are different. 217 # winbind_separator: / 200 218 201 219 # What is the accounting backend to use