Thanks Florent. if this has puzzled anyone else.... We changed the zLOG.py script, and Lo! logging is now in localtime. A quick scan through various python script directories shows time functions are all hardcoded as "time.gmtime". Obviously to be consistent, all scripts would have to be modified to "time.localtime", else yur zope envt would be in a right mess. I think someone raised the request prior to 2.4.3 (ie, "Could it be included in 2.4.3?"). One solution of course is to set your machine's "GMT" as the actual local time, and then not need a timezone setting. In our case, all our machines are NTP sync'ed, so we're stuck with GMT. cheers Graham -----Original Message----- From: Florent Guillaume [mailto:fg@nuxeo.com] Sent: Wednesday, 19 December 2001 3:59 To: zope@zope.org Subject: Re: [Zope] Time Zone question If you really want to change this, change the log_time function in zLog.py to use localtime instead of gmtime. Florent Graham King <Graham.King@team.ozemail.com.au> wrote:
maybe dumb question?
How do I get zope to operate with local time zone?
I see at start up I get two time zones, GMT and local, as follows:
2001-12-18T03:29:54 INFO(0) ZServer HTTP server started at Tue Dec 18 14:29:54 2001
When adding anything, "Last modified" records in GMT. This is confusing our developers, and me, since everything seems to be done at some ungodly hour in the middle of the night.
PS. I've tried setting TZ in the startup script. -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 10 http://nuxeo.com mailto:fg@nuxeo.com
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )