Index: /pykota/trunk/docs/repykota.sgml
===================================================================
--- /pykota/trunk/docs/repykota.sgml (revision 2551)
+++ /pykota/trunk/docs/repykota.sgml (revision 2844)
@@ -7,5 +7,5 @@
To account for print usage is good, however there must be a way to easily
- query the Quota Storage Server and generate
+ query the print quota database and generate
reports describing current usage for every user on every printer.
Index: /pykota/trunk/docs/warnpykota.sgml
===================================================================
--- /pykota/trunk/docs/warnpykota.sgml (revision 2147)
+++ /pykota/trunk/docs/warnpykota.sgml (revision 2844)
@@ -38,5 +38,5 @@
message. He can specify a printer name's filter to check his quota only
on specific printers. If a normal user uses the --groups command line
- argument, then for each group he is a member of in the Quota Storage, each
+ argument, then for each group he is a member of in the print quota database, each
group member may receive a warning message. You can take care of this if this
becomes annoying by forbidding normal users to launch the warnpykota
Index: /pykota/trunk/docs/installation.sgml
===================================================================
--- /pykota/trunk/docs/installation.sgml (revision 2842)
+++ /pykota/trunk/docs/installation.sgml (revision 2844)
@@ -13,5 +13,5 @@
First you have to determine which machine will be the PyKota
- Storage Server. The Storage Server is the host responsible
+ database server. The database server is the host responsible
for keeping a centralized database of print usage for all your printers, users and groups.
@@ -19,5 +19,11 @@
Then you have to list all the Print Servers for which
- you plan to use print quota facilities.
+ you plan to use print quota facilities.
+
+
+
+ With most database backends, several print servers can share a single database, however
+ as we'll see later this is not possible if you choose to use SQLite
+ as your print quota database backend.
@@ -102,5 +108,5 @@
modify the /etc/postgresql/postgresql.conf file, which is
self documented and easy to modify too. Allowing TCP/IP connections
- is not necessary though if your Quota Storage Server and your Print Server are
+ is not necessary though if your print quota database server and your Print Server are
the very same host.
@@ -152,17 +158,17 @@
Now that your PostgreSQL server is up and running, and
- is waiting for your connections, you have to create the Quota Storage DataBase.
+ is waiting for your connections, you have to create the print quota database.
To do so, you'll have to feed PostgreSQL with the
pykota-1.24/initscripts/postgresql/pykota-postgresql.sql file.
- This file will create a Quota DataBase administrator in the PostgreSQL system, then create an empty
- Quota DataBase and set some permissions on it. The Quota DataBase administrator
- is the PostgreSQL's user used to manage the Quota database.
- The Quota DataBase Administrator is not present in the Quota Database
+ This file will create a print quota database administrator in the PostgreSQL system, then create an empty
+ print quota database and set some permissions on it. The print quota database administrator
+ is the PostgreSQL's user used to manage the quota database.
+ The print quota database Administrator is not present in the quota database
itself, he is only defined in PostgreSQL and don't
- have to exist on any system, nor in the Quota DataBase. His default name
+ have to exist on any system, nor in the print quota database. His default name
is pykotaadmin.
- A Quota Storage read-only user is also created under the name of pykotauser.
+ A print quota database read-only user is also created under the name of pykotauser.
This read-only user is used by PyKota to connect to the
- Quota Storage when an user who is not a PyKota administrator
+ print quota database when an user who is not a PyKota administrator
a PyKota administrator is an user who can read the ~pykota/pykotadmin.conf file.
launches a pykota command. This prevents normal
@@ -218,5 +224,5 @@
pykotaadmin and pykotauser users.
Otherwise any user able to connect to
- PostgreSQL on your Quota Storage Server
+ PostgreSQL on your print quota database server
could connect to the quota database, and either see it, or even modify it without problem.
@@ -257,8 +263,8 @@
- If no error occured, then your Quota DataBase is ready to be used.
- Now you can let the Quota Storage Server alone, the remaining work
+ If no error occured, then your print quota database is ready to be used.
+ Now you can let the print quota database server alone, the remaining work
will have to be done on each one of the print servers which will
- use this particular Quota Storage Server.
+ use this particular print quota database server.
Tip
@@ -278,5 +284,5 @@
Any LDAP server, and particularly OpenLDAP, can be used
- as a Quota Storage Backend.
+ as a print quota database backend.
Some other LDAP servers can be used, but this is currently untested in production.
@@ -289,5 +295,5 @@
- To use OpenLDAP as your Quota Storage Backend, you have to copy the
+ To use OpenLDAP as your print quota database backend, you have to copy the
pykota/initscripts/ldap/pykota.schema into OpenLDAP's
schemas directory.
@@ -399,8 +405,8 @@
- If no error occured, then your Quota DataBase is ready to be used.
- Now you can let the Quota Storage Server alone, the remaining work
+ If no error occured, then your print quota database is ready to be used.
+ Now you can let the print quota database server alone, the remaining work
will have to be done on each one of the print servers which will
- use this particular Quota Storage Server.
+ use this particular print quota database server.
Tip
@@ -473,5 +479,14 @@
- That's all ! For more details, please refer to pykota/initscripts/sqlite/README.sqlite.
+ If no error occured, then your print quota database is ready to be used.
+ In case you need them, additional instructions are available in pykota/initscripts/sqlite/README.sqlite
+
+ Tip
+
+ If an error occured, maybe your SQLite version is too old, or
+ an unexpected problem (like a bug) happened. Please contact us via email so that we
+ can try to fix the problem. Thanks in advance.
+
+
@@ -481,5 +496,5 @@
- A Berkeley DB Storage Backend is planned, but it actually
+ A Berkeley DB backend is planned, but it actually
doesn't exist. It seems that remote storage won't be possible with such a backend,
so in other terms this means that you will have a different quota database on
@@ -524,5 +539,5 @@
- Quota Storage client libraries, depending on your Quota Storage Backend :
+ print quota database client libraries, depending on your print quota database backend :
@@ -533,5 +548,5 @@
PostgreSQL client libraries. They must match the PostgreSQL
- version used on your Quota Storage Server.
+ version used on your print quota database server.
@@ -539,6 +554,4 @@
The PygreSQL python module.
- It must have been compiled against the same
- PostgreSQL client libraries.
PygreSQL is normally included in
PostgreSQL, but you may want to
@@ -556,5 +569,5 @@
OpenLDAP client libraries. They must match
- the OpenLDAP version used on your Quota Storage Server.
+ the OpenLDAP version used on your print quota database server.
@@ -562,6 +575,4 @@
The Python-LDAP python module.
- It must have been compiled against the same
- OpenLDAP client libraries.
You may download this module from http://python-ldap.sourceforge.net
@@ -572,5 +583,19 @@
- MySQL backend : Supported but not documented yet.
+ MySQL backend :
+
+
+
+ MySQL client libraries. They must match the MySQL
+ version used on your database server.
+
+
+
+
+ The Python-MySQL python module, version 1.2.x or higher.
+ You can download it from http://sourceforge.net/projects/mysql-python
+
+
+