Dieter, Is this improved at all by Fred's latest zZLOG-removal checkins? If not, I will open a collector issue.
- C On Fri, 2004-04-02 at 03:34, Dieter Maurer wrote: > Zope 2.7 delays access to log files until Zope is properly set up. > This means: log files cannot be used to analyse startup problems. > > The official advice to analyse startup problems is to start > Zope in the foreground and interpret the console log messages. > > However, this does *NOT* work when Zope is not running in > debug mode. "Zope.Startup.ZopeStarter.setupStartupHandler" > expressly suppresses messages to "stderr" when Zope > is not running in debug mode. > > Apparently, we do not have an easy way to analyse startup problems > for Zope in production mode. > In my view, this is really bad. > > > Please provide a way to control how startup messages should > be handled. The best place would be a file (at least for > all installations that do not start Zope as root and later > switch the effective user). > > I suggest to always use the standard log file unless > told otherwise by an explicit configuration option. _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
