Zope has it's own layer on top of the system's time zone. Sometimes this causes problems when you're using a time zone on the system that Zope doesn't know about. Usually this can be fixed by using better- known name for the time zone such as GMT+4. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users[/quote]
Thanks for the information. I just tried GMT-5 and GMT and set both the system and HW clock and restarted and rebooted the system but still Zenoss shows it is off (early) by 4 hours. Wonder if this matters since it is a VMWare Image running on an ESX server? 2.0 didnt have this issue/functionality. Question is does ZOPE determine the schedules of maint. windows and alerts? IF it doesnt then I dont really care. Otherwise sort of a PITA as have to adjust all my maint. windows etc to be 4 hours earlier then the correct time. Appreciate your help on this issue Cheers cp -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=13625#13625 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
