I tried running pymsn-t on a port that was already in use and that revealed two problems.
1) Even with debugLevel 2, the only output I got was "removing stale pidfile". I had to set debugLevel to 3 to get the actual traceback (and other debug prints). The explanation of debugLevel in my configuration file is this: <!-- The logging level 0 -> No logging 1 -> Log tracebacks 2 -> Log tracebacks, warnings and errors 3 -> Log all sorts of informational (mostly useless stuff) 4 -> Log the MSN protocol code sent --> So which one is correct? The config file or the code? 2) The errors were logged to stdout even though I started the thing with: /usr/bin/python /usr/lib/python2.4/site-packages/pymsn-t/pymsn-t.py \ -c /etc/jabber/pymsn-t.xml -l /var/log/jabber/pymsn-t.log Setting the log file name in the configuration file DOES work. Regards, Maurice. P.S.: If there's a better place to report this, please tell me. -- Maurice van der Pot Gentoo Linux Developer [EMAIL PROTECTED] http://www.gentoo.org Creator of BiteMe! [EMAIL PROTECTED] http://www.kfk4ever.com
pgp91j3ZHBLum.pgp
Description: PGP signature
_______________________________________________ py-transports mailing list [email protected] http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
