[kronolith] (no subject)

[Clive Eisen]

Unix epoch for a guess

The 1-tick-per-second clock of UNIX is good only until January 18, 2038
--
Clive
----- Original Message -----
From: "Nate Mollring" <nmollring@cennecs.org>
To: <kronolith@lists.horde.org>
Sent: Tuesday, July 30, 2002 5:06 PM
Subject: [kronolith] (no subject)


> Zitat von Chuck Hagenbuch <chuck@horde.org>:
>
> > Quoting Nate Mollring <nmollring@cennecs.org>:
> >
> Well I found a way to get it to work now.  I changed the year from 9999 to
2030
> in Event.php and it works.  Any idea why it works with that year and not
9999--
> or even 2040 and higher won't work.
> Nate
>
>
> > > I'm running an e-smith 5.1.2 box with php 4.1.2, imp 3.1, kronolith,
> > and
> > > nag. In kronolith when I create a new or edit an event, recur until
> > --no
> > > end date won't work.  When I use 'no end date' the database (via
> > > phpmyadmin) shows a date in 1969--then the event won't recur
correctly.
> >
> > > I've installed the latest Event.php and I still have the same problem.
> > Oh,
> > > and the database I'm using is MySql.  Would switching to Mcal help?
> > > Switching to mcal doesn't look like an easy project, but if that's
what
> >
> > > needs to be done...
> >
> > I _think_ this is a bug that's been fixed in CVS.
>
> Confirmed.
>
> Jan.
>
>
> --
> Central Nebraska Community Services
> http://www.welcome2cncs.com
>
> --
> Kronolith mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: kronolith-unsubscribe@lists.horde.org
>