Changeset 3210 for pykota/trunk

Show
Ignore:
Timestamp:
07/20/07 10:55:40 (17 years ago)
Author:
jerome
Message:

Added more items.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • pykota/trunk/qa-assistant/pykota.xml

    r3209 r3210  
    325325      </description> 
    326326    </entry> 
     327    <entry name="Modify PyKota's configuration files" display="true"> 
     328      <states> 
     329        <state name="Pass">PyKota configuration files are correct</state> 
     330        <state name="Fail">PyKota configuration files are incorrect</state> 
     331      </states> 
     332      <description> 
     333        PyKota's configuration files must be adapted to your own configuration, 
     334        and you can do this with any text editor of your choice. 
     335        In particular, the usernames and passwords used for the readonly 
     336        and the read+write database accounts have to be put there. 
     337        You'll also define the print administrator's name and email address, 
     338        and define the hostname of your SMTP server. 
     339        Finally many configuration directives must be checked or modified 
     340        to control PyKota's behavior. To help you in doing this, the 
     341        sample configuration files which you have installed are 
     342        extensively documented with comments. 
     343      </description> 
     344    </entry> 
     345    <entry name="Setup the cupspykota backend" display="true"> 
     346      <states> 
     347        <state name="Pass">cupspykota is installed</state> 
     348        <state name="Fail">cupspykota is not installed</state> 
     349      </states> 
     350      <description> 
     351        To be able to route printing traffic through PyKota, CUPS must 
     352        be told that PyKota is installed. To do this, we must 
     353        add the 'cupspykota' backend wrapper to CUPS' backend directory, 
     354        usually '/usr/lib/cups/backend'. 
     355        To do this the easiest is to create a symbolic link : 
     356        'ln -s /usr/share/pykota/cupspykota /usr/lib/cups/backend/' 
     357        and then '/etc/init.d/cupsys restart' 
     358      </description> 
     359    </entry> 
     360    <entry name="Verify that PyKota is known to CUPS" display="true"> 
     361      <states> 
     362        <state name="Pass">PyKota is known to CUPS</state> 
     363        <state name="Fail">PyKota is not known to CUPS</state> 
     364      </states> 
     365      <description> 
     366        Once you've installed the 'cupspykota' backend wrapper and 
     367        restarted CUPS. You may want to check that CUPS recognizes it. 
     368        Just look at http://cupsserver.example.com:631/admin/ to see 
     369        if any 'PyKota managed' device is available. If none is available 
     370        the permissions on the cupspykota backend are probably incorrect 
     371        for your setup : the user CUPS runs as MUST be able to exectute 
     372        the 'cupspykota' backend wrapper, as well as to read both 
     373        PyKota's configuration files. 
     374      </description> 
     375    </entry> 
    327376  </category>   
    328377</checklist>