Changeset 1021 for pykota/trunk/docs
- Timestamp:
- 06/10/03 18:37:54 (21 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
pykota/trunk/docs/installation.sgml
r1015 r1021 131 131 To do so, you'll have to feed <application>PostgreSQL</application> with the 132 132 <filename>pykota-x.xx/initscripts/postgresql/pykota-postgresql.sql</filename> file. 133 This file will create a Quota DataBase administrator and a Quota DataBase user 134 in the <application>PostgreSQL</application> system, then create an empty 133 This file will create a Quota DataBase administrator in the <application>PostgreSQL</application> system, then create an empty 135 134 Quota DataBase and set some permissions on it. The Quota DataBase administrator 136 will be able to add printers, users and groups to the Quota DataBase, while 137 the Quota DataBase user will be used to update the print quota usage 138 in the Quota DataBase. None of these two users is present in the Quota Database 139 itself, they are only defined in <application>PostgreSQL</application> and don't 140 have to exist on any system, nor in the Quota DataBase. Their default names 141 are <literal>pykotaadmin</literal> for the administrator and <literal>pykotauser</literal> 142 for the user. The database which will be created will be named <literal>pykota</literal>. 135 is the <application>PostgreSQL</application>'s user used to manage the Quota database. 136 The Quota DataBase Administrator is not present in the Quota Database 137 itself, he is only defined in <application>PostgreSQL</application> and don't 138 have to exist on any system, nor in the Quota DataBase. His default names 139 is <literal>pykotaadmin</literal>. 140 The database which will be created will be named <literal>pykota</literal> by default. 143 141 <note> 144 142 <title>Note</title> … … 179 177 For security reasons, you may want to set passwords in 180 178 <application>PostgreSQL</application> for the 181 <literal>pykotaadmin</literal> and <literal>pykotauser</literal>182 users.Otherwise any user able to connect to179 <literal>pykotaadmin</literal> user. 180 Otherwise any user able to connect to 183 181 <application>PostgreSQL</application> on your Quota Storage Server 184 could connect to the quota database as one of themand modify it without problem.182 could connect to the quota database as this user, and modify it without problem. 185 183 </para> 186 184 187 185 <para> 188 186 To do so, just type the following lines while still being at the <application>psql</application> 189 prompt (replace the password svalues by your own) :187 prompt (replace the password values by your own) : 190 188 <screen> 191 189 pykota=# ALTER USER pykotaadmin PASSWORD 'somepassword'; 192 ALTER USER193 pykota=# ALTER USER pykotauser PASSWORD 'anotherpassword';194 190 ALTER USER 195 191 pykota=# \q … … 253 249 254 250 <para> 255 An <application>LDAP</application> Storage Backend is planned, but it actually 256 doesn't exist. Some people may already be working on this, though. 251 An <application>LDAP</application> Storage Backend is currently under heavy work. 252 You can already give a look at the LDAP schema which was defined for PyKota. 253 Full support for LDAP in PyKota should be OK by the end of July 2003, if all 254 continues to go well. 257 255 </para> 258 256 </sect2> … … 374 372 375 373 $Log$ 374 Revision 1.15 2003/06/10 16:37:54 jalet 375 Deletion of the second user which is not needed anymore. 376 Added a debug configuration field in /etc/pykota.conf 377 All queries can now be sent to the logger in debug mode, this will 378 greatly help improve performance when time for this will come. 379 376 380 Revision 1.14 2003/06/05 07:12:29 jalet 377 381 Reorganization of directories