Changeset 2126 for pykota

Show
Ignore:
Timestamp:
03/05/05 19:54:54 (20 years ago)
Author:
jalet
Message:

Improved the installation documentation.
Now checkdeps also checks for the presence of GhostScript?, which
may be needed if PyKota's bannering facility is used or if some
printer driver produces non-DSC compliant PostScript?.

Location:
pykota/trunk
Files:
3 modified

Legend:

Unmodified
Added
Removed

  • pykota/trunk/checkdeps.py

    r2061 r2126  
    2424# 
    2525# $Log$ 
     26# Revision 1.6  2005/03/05 18:54:54  jalet 
     27# Improved the installation documentation. 
     28# Now checkdeps also checks for the presence of GhostScript, which 
     29# may be needed if PyKota's bannering facility is used or if some 
     30# printer driver produces non-DSC compliant PostScript. 
     31# 
    2632# Revision 1.5  2005/02/14 23:37:58  jalet 
    2733# Added a check for the presence of pythn-psyco 
    … …  
    98104                       ("Python-Psyco", "psyco", "Python-Psyco speedups parsing of print files, you should use it.\nSee http://psyco.sourceforge.net/"), 
    99105                     ] 
    100     commandstocheck = [ ("SNMP Tools", "snmpget", "SNMP Tools are needed if you want to use SNMP enabled printers."),  
     106    commandstocheck = [ ("GhostScript", "gs", "Depending on your configuration, GhostScript may be needed in different parts of PyKota."), 
     107                        ("SNMP Tools", "snmpget", "SNMP Tools are needed if you want to use SNMP enabled printers."),  
    101108                        ("Netatalk", "pap", "Netatalk is needed if you want to use AppleTalk enabled printers.") 
    102109                      ] 

  • pykota/trunk/docs/installation.sgml

    r2117 r2126  
    122122        Of course if your print server and your database servers have different <acronym>IP</acronym> 
    123123        addresses, you have to replace the <literal>127.0.0.1</literal> address above with your print 
    124         server's <acronym>IP</acronym> address. 
     124        server's <acronym>IP</acronym> address. As an alternative, you could still keep these 
     125        lines and add similar lines with other <acronym>IP</acronym> addresses if have several 
     126        print servers for which you want a single centralized database. 
    125127        <tip> 
    126128          <title>Tip</title> 
    … …  
    297299          <title>Note</title> 
    298300          <para> 
    299             If you use RPM or DEB packages, usually the 
    300             <filename>pykota.schema</filename> file gets installed into the 
    301             <filename>/usr/share/pykota/ldap</filename> directory, along  
    302             with a README file. 
     301            If you use RPM or DEB packages, the 
     302            <filename>pykota.schema</filename> file is usually installed into the 
     303            <filename>/usr/share/pykota/ldap</filename> directory, along 
     304            with a README file, and may also be installed automatically in 
     305            your <acronym>LDAP</acronym> server's schemas directory. 
    303306          </para> 
    304307        </note>   
    … …  
    379382        <command>ldapadd</command> command, or with some specialized tool 
    380383        like <command>gq</command>. You can look at the <filename>initscripts/ldap/pykota-sample.ldif</filename> 
    381         file to see what minimal branches are necessary. 
     384        file to see which minimal branches are necessary. 
    382385        <note> 
    383386          <title>Note</title> 
    384387          <para> 
    385388            If you use RPM or DEB packages, usually the 
    386             <filename>pykota-sample.ldif</filename> file gets installed into the 
     389            <filename>pykota-sample.ldif</filename> file is installed into the 
    387390            <filename>/usr/share/pykota/ldap</filename> directory, along  
    388391            with a README file. 
    … …  
    447450        <listitem> 
    448451          <para> 
    449             <application>CUPS</application> version 1.1 or above, or <application>LPRng</application> 
     452            <application>CUPS</application> version 1.1.14 or above, or <application>LPRng</application> 
    450453            version 3.8.27 or above (it probably works with older versions but this is untested). 
    451454            You can download them from <ulink url="http://www.cups.org">http://www.cups.org</ulink> 
    … …  
    455458        <listitem> 
    456459          <para> 
    457             Python version 2.1 or above. 
     460            <application>Python</application> version 2.1 or above. 
    458461            You can download it from <ulink url="http://www.python.org">http://www.python.org</ulink>. 
     462            While <application>PyKota</application> itself will try to preserve compatibility 
     463            with <application>Python</application> version 2.1 for the near future, some <application>Python</application> 
     464            modules which are needed by <application>PyKota</application> may mandate the use of a more recent version 
     465            of this language. 
    459466          </para> 
    460467        </listitem>   
    … …  
    570577        <listitem> 
    571578          <para> 
     579            The <application>Python Imaging Library - PIL</application> module.  
     580            You can download it from <ulink url="http://www.pythonware.com">http://www.pythonware.com</ulink>. 
     581          </para> 
     582        </listitem>   
     583        <listitem> 
     584          <para> 
    572585            The <application>PyOSD</application> Python module.  
    573586            You can download it from <ulink url="http://repose.cx/pyosd/">http://repose.cx/pyosd/</ulink>. 
    … …  
    635648      In a future release, this documentation will include the complete 
    636649      reference for all configuration fields available. Keep in mind that 
    637       PyKota can be really heavily customized, and can delegate some work 
     650      <application>PyKota</application> can be really heavily customized, and can delegate some work 
    638651      to any external command of your choice. 
    639652    </para> 
    … …  
    648661      define options either globally so that they apply to all printers, 
    649662      or on a per printer basis. Please see the sample configuration files 
    650       to see what I mean. In the simplest form, only a global section is 
     663      to see what I mean. In the simplest form, only a <literal>[global]</literal> section is 
    651664      needed. In more complex configurations, you will have to create  
    652665      one section per printer. Each section in the configuration files 
    … …  
    657670     
    658671    <para> 
    659       After you have modified PyKota's configuration files, you have to 
     672      After you have modified <application>PyKota</application>'s configuration files, you have to 
    660673      double check their permissions, otherwise your installation may be 
    661674      insecure or may not work at all. 
    … …  
    664677      readable by anyone. If normal users read this file, at best they 
    665678      will learn the username and optional password of the read-only 
    666       database user, so they won't be allowed to do any harm. 
     679      database user. This means that beside being allowed to read all the contents of 
     680      the quota database, they won't be allowed to modify or delete it. 
    667681      On the other hand, the <filename>~pykota/pykotadmin.conf</filename> 
    668682      file contains the read-write user's identity and password. You must then 
    … …  
    692706    </para> 
    693707     
     708    <para> 
     709      Don't forget to restart your print server sofware if you changed group membership for the user it runs 
     710      as, otherwise your change wouldn't be taken into account. 
     711    </para> 
    694712     
    695713    <para> 
    … …  
    702720       
    703721      <para> 
    704         From version 1.16alpha7 on, configuring PyKota to integrate 
    705         within CUPS is more than easy. 
     722        From version 1.16alpha7 on, configuring <application>PyKota</application> to integrate 
     723        within <application>CUPS</application> is more than easy. 
    706724      </para> 
    707725       
    708726      <para> 
    709727        You just have to create a symbolic link to the <filename>cupspykota</filename> 
    710         command in CUPS' backend directory : 
     728        command in <application>CUPS</application>' backend directory : 
    711729        <screen>         
    712730$ cd /usr/lib/cups/backend         
    … …  
    831849 
    832850$Log$ 
     851Revision 1.33  2005/03/05 18:54:54  jalet 
     852Improved the installation documentation. 
     853Now checkdeps also checks for the presence of GhostScript, which 
     854may be needed if PyKota's bannering facility is used or if some 
     855printer driver produces non-DSC compliant PostScript. 
     856 
    833857Revision 1.32  2005/02/28 23:17:40  jalet 
    834858Improved documentation 

  • pykota/trunk/README

    r2119 r2126  
    241241 
    242242  You can now purchase 8x5x365@NextBusinessDay Technical 
    243 Support Contracts from us. The yearly fee is computed with   
    244 the following formula : 
     243  Support Contracts from us. The yearly fee is computed with   
     244  the following formula : 
    245245 
    246246  (100.0 * NbPrintServers) + (2.5 * NbPrinters) + (0.04 * NbUsers) EUROS. 
    247247   
    248248  This fee includes the VAT, and a free subscription to official   
    249 PyKota packages.   
     249  PyKota packages.   
    250250 
    251251  Please send an email to alet@librelogiciel.com if you're 
    252 interested in purchasing such a contract.    
     252  interested in purchasing such a contract.    
     253 
     254  Remember that purchasing a support contract for Free Software like PyKota 
     255  is a great way to show your appreciation for the work already being done  
     256  on this project, and will help to improve this software in the future. 
    253257 
    254258============================================================ 
    … …  
    643647 
    644648  - Kanakorn Horsiritham developped phpPykotaAdmin which is  
    645     a web based database independant administrative GUI : 
     649    a web based database independant administrative GUI, 
     650    written in PHP. 
    646651   
    647652      http://opensource.psu.ac.th/~kanakorn/mambo/ 
     653       
     654    He was also kind enough to write an installation guide   
     655    in english for CUPS and PyKota with phpPykotaAdmin on Fedora 
     656    Core 3. You'll find this document on the same website. 
     657     
     658    This great software currently at version 0.3 is a wonderful 
     659    basis for an administrative GUI since it only depends on  
     660    PyKota commands to be present to successfully manage 
     661    PyKota's database.  
    648662   
    649663Additionnal software will be listed here when they will be