Changeset 2045 for pykota/trunk

Show
Ignore:
Timestamp:
01/26/05 07:45:54 (20 years ago)
Author:
jalet
Message:

Moved the diagnostic information to the top of the file.

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • pykota/trunk/FAQ

    r1947 r2045  
    22 
    33  # $Id$ 
     4   
     5  * How can I diagnose the problem when something goes wrong ? 
     6   
     7    Put "LogLevel debug2" in cupsd.conf (usually in /etc/cups/). 
     8    Then put "logger: stderr", "debug: yes" and  
     9    "crashrecipient: youremailaddress" in /etc/pykota/pykota.conf. 
     10    Finally restart CUPS. 
     11    CUPS' error_log file will now contain many informations which 
     12    will help diagnose your problem. You will receive failure 
     13    notices by email, and you can send all this to us for 
     14    diagnostic. 
     15     
     16    For LPRng, better to put "logger: system" in pykota.conf so 
     17    that all debug messages for PyKota will go to syslog. 
    418   
    519  * Nothing prints when my printer is in PowerSave mode, what 
    … …  
    3347    reinstall the software. It should work. 
    3448     
    35   * How can I diagnose the problem when something goes wrong ? 
    36    
    37     Put "LogLevel debug2" in cupsd.conf (usually in /etc/cups/). 
    38     Then put "logger: stderr", "debug: yes" and  
    39     "crashrecipient: youremailaddress" in /etc/pykota/pykota.conf. 
    40     Finally restart CUPS. 
    41     CUPS' error_log file will now contain many informations which 
    42     will help diagnose your problem. You will receive failure 
    43     notices by email, and you can send all this to us for 
    44     diagnostic. 
    45      
    46     For LPRng, better to put "logger: system" in pykota.conf so 
    47     that all debug messages for PyKota will go to syslog. 
    48    
    4949  * Why doesn't CUPS under Debian Woody automatically 
    5050    detects PyKota managed devices ?