"J.O. Aho" <user@example.net> wrote in
news:5mrj3oFf15biU1@mid.individual.net:

> nonce999 wrote:
>> not not.
>> the problem is not in the client but in the server.
>
> You get the script better working for most visitors if they get
> their own time instead of the servers.
>
>
>> the server turn 2 hour behind randomly.
>
> Only option would be if the servers hardware clock is broken and
> you run the ntp update not enough times to keep the time right.
>
i not would write a any clock but a clock with server time.


> Apache itself won't affect the time, it will always use the time
> that the system says it has.
>
> PHP won't temper with the time, it do read the system time too,
> but of course ill written PHP scripts may convert the system
> time badly when it tries to change timezones.
the strange thing is that the system timetable remains corrected
(f.e. 12:00) while the timetable of the script behind goes of two
hours some times (f.e. 10:00)
it is very strange but it is


> Still, the best solution would be to not initialize the time
> based on the servers clock, but on the clients clock.
i not would write a any clock but a clock with server time.



--
http://interno.altervista.org
http://midiquiz.altervista.org