[Zope] ZLOGGER related BUG

[michel@digicool.com]

Robin Becker <robin@jessikat.demon.co.uk> writes:

> OK after using Anthony Baxters suggestion I have some files in lib/python/ZLogger
> 
> but I get this on startup
> C:\Python\devel\Zope>python z2.py
> Traceback (innermost last):
>   File "z2.py", line 349, in ?
>     import zLOG, ZLogger
>   File "C:\Python\devel\ZOPE\lib\python\ZLogger\__init__.py", line 86, in ?
>     import ZLogger
>   File "C:\Python\devel\ZOPE\lib\python\ZLogger\ZLogger.py", line 7, in ?
>     loggers = (stupidFileLogger.stupidFileLogger(), syslogLogger.syslogLogger(),)
>   File "C:\Python\devel\ZOPE\lib\python\ZLogger\syslogLogger.py", line 12, in __init__
>     self.client = syslog_client()
>   File "C:\Python\devel\ZOPE\lib\python\ZLogger\syslog.py", line 146, in __init__
>     self.socket = socket.socket (socket.AF_UNIX, socket.SOCK_STREAM)
> AttributeError: AF_UNIX
> 

Argh.  My bad, The syslogd logger is accidently turned on by default,
and Windows doesn't support Unix Domain Sockets (obviously.. ;)  On
startup, try:

python1.5.2 z2.py ZSYSLOG_SERVER=127.0.0.1:514

This will cause it to use UDP sockets (which windows does support) and 
will redirect the logging packets to your localhost, which will just
then vanish in thin air.  Alternatively, you could point this to a
configured unix machine and do syslog style logging.

The solution is, of course, to be able to turn the whole thing off.
I'll fix this today.

-Michel

> -- 
> Robin Becker
> 
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://www.zope.org/mailman/listinfo/zope
> 
> (For developer-specific issues, use the companion list,
> zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )