Changeset 1099 for pykota/trunk/docs/installation.sgml
- Timestamp:
- 07/25/03 12:41:30 (21 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
pykota/trunk/docs/installation.sgml
r1052 r1099 116 116 is the case, then the best thing you can do is to ask your <firstterm>Network Administrator</firstterm> 117 117 to not filter the IP port used by <application>PostgreSQL</application>, which is 118 usually port 5432/tcp.118 usually port <literal>5432/tcp</literal>. 119 119 <note> 120 120 <title>Note</title> … … 138 138 have to exist on any system, nor in the Quota DataBase. His default names 139 139 is <literal>pykotaadmin</literal>. 140 A Quota Storage read-only user is also created under the name of <literal>pykotauser</literal>. 141 This read-only user is used by <application>PyKota</application> to connect to the 142 Quota Storage when a non-root user launches a pykota command. This prevents normal 143 users from being able to modify their own, or other users', quota information. 140 144 The database which will be created will be named <literal>pykota</literal> by default. 141 145 <note> … … 177 181 For security reasons, you may want to set passwords in 178 182 <application>PostgreSQL</application> for the 179 <literal>pykotaadmin</literal> user.183 <literal>pykotaadmin</literal> and <literal>pykotauser</literal> users. 180 184 Otherwise any user able to connect to 181 185 <application>PostgreSQL</application> on your Quota Storage Server 182 could connect to the quota database as this user, andmodify it without problem.186 could connect to the quota database, and either see it, or even modify it without problem. 183 187 </para> 184 188 185 189 <para> 186 190 To do so, just type the following lines while still being at the <application>psql</application> 187 prompt (replace the password values by your own ) :191 prompt (replace the password values by your own, and do the same for the <literal>pykotauser</literal> user) : 188 192 <screen> 189 193 pykota=# ALTER USER pykotaadmin PASSWORD 'somepassword'; … … 203 207 take any other step as needed. Please refer to <application>PostgreSQL</application>'s 204 208 documentation for details. Also if <application>PyKota</application>'s configuration 205 file is readable by anyone with access on your file system, a local user could209 file <filename>/etc/pykota/pykotadmin.conf</filename> is readable by anyone with access on your file system, a local user could 206 210 create some script to modify his own print quota. 207 211 <warning> … … 274 278 275 279 <para> 276 Then you have to modify PyKota's configuration file <filename>/etc/pykota.conf</filename> 280 Then you have to modify PyKota's configuration files <filename>/etc/pykota/pykota.conf</filename> 281 and <filename>/etc/pykota/pykotadmin.conf</filename> 277 282 to include LDAP specific options. You may want to give a look at 278 283 <filename>pykota/conf/pykota.conf.sample</filename> to see all the options that are … … 361 366 <listitem> 362 367 <para> 363 MySQLbackend : TODO368 LDAP backend : TODO 364 369 </para> 365 370 </listitem> 366 371 <listitem> 367 372 <para> 368 LDAPbackend : TODO373 MySQL backend : TODO 369 374 </para> 370 375 </listitem> … … 407 412 408 413 $Log$ 414 Revision 1.18 2003/07/25 10:41:29 jalet 415 Better documentation. 416 pykotme now displays the current user's account balance. 417 Some test changed in ldap module. 418 409 419 Revision 1.17 2003/06/30 21:44:18 jalet 410 420 1.09 is out !