bobobase_modification_time stuck after system date change (back 1 month)
Hi, I installed a brand new Zope on a server (redhat) on which the system date was 1 month ahead (2003 March 3 for today). The system admin just corrected the system date/time today, but when creating a new object after this, its bobobase_modification_time() is still shifted 1 month ahead, when DateTime() shows the (corrected) system date !!! Even after a Zope restart. Why does this happend ? How can I fix this ? Many thanks in advance for any hint ! --Gilles
Hi, This is a temporary solution. It is a hotfix-like product for bobobase_modification_time function. My product overwrites the original function from App.PersistentExtra. The only change made is that if the bobobase_modification_time() of an object is in the future then it returns the current server time (DateTime). Use this product until 3 March 2003... :) VeCo ----- Original Message ----- From: "Gilles Lenfant" <gilles@pilotsystems.net> To: <zope@zope.org> Sent: Tuesday, February 04, 2003 7:31 PM Subject: [Zope] bobobase_modification_time stuck after system date change (back 1 month)
Hi,
I installed a brand new Zope on a server (redhat) on which the system date was 1 month ahead (2003 March 3 for today). The system admin just corrected the system date/time today, but when creating a new object after this, its bobobase_modification_time() is still shifted 1 month ahead, when DateTime() shows the (corrected) system date !!! Even after a Zope restart. Why does this happend ? How can I fix this ?
Many thanks in advance for any hint !
--Gilles
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
----- Original Message ----- From: "Cornel Nitu" <c.nitu@finsiel.ro> To: "Zope" <zope@zope.org> Sent: Wednesday, February 05, 2003 10:24 AM Subject: Re: [Zope] bobobase_modification_time stuck after system date change (back 1 month) | ----- Original Message ----- | From: "Gilles Lenfant" <gilles@pilotsystems.net> | To: <zope@zope.org> | Sent: Tuesday, February 04, 2003 7:31 PM | Subject: [Zope] bobobase_modification_time stuck after system date change | (back 1 month) | | | > Hi, | > | > I installed a brand new Zope on a server (redhat) on which the system date | > was 1 month ahead (2003 March 3 for today). | > The system admin just corrected the system date/time today, but when | > creating a new object after this, its bobobase_modification_time() is | still | > shifted 1 month ahead, when DateTime() shows the (corrected) system date | !!! | > Even after a Zope restart. | > Why does this happend ? | > How can I fix this ? | > | > Many thanks in advance for any hint ! | > | > --Gilles || > | | Hi, | This is a temporary solution. It is a hotfix-like product for | bobobase_modification_time function. | My product overwrites the original function from App.PersistentExtra. | The only change made is that if the bobobase_modification_time() of an | object is in the future then it returns the current server time (DateTime). | Use this product until 3 March 2003... :) | | | VeCo | Many thanks, but I reinstalled Zope before your post, and all's OK now. Hopefully, this was a development instance, not a production one ! Zope doc should warn loudly about the system clock issue before installing a server. --Gilles
participants (2)
-
Cornel Nitu -
Gilles Lenfant