From when have reinstalled 1,3 Apache and 4.4.7 Php from time to time
Apache or Php me they put behind their timetable of a pair
of hour while the system timetable remains corrected.
Then I must stop and restart the Apache service in order to correct
it.
Which thing can have happened? Where I can inquire?

Use the timetable of the serveur with this script:

http://interno.altervista.org/module...name=OraEsatta

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

nonce999 wrote:
> From when have reinstalled 1,3 Apache and 4.4.7 Php from time to time
> Apache or Php me they put behind their timetable of a pair
> of hour while the system timetable remains corrected.
> Then I must stop and restart the Apache service in order to correct
> it.
> Which thing can have happened? Where I can inquire?
>
> Use the timetable of the serveur with this script:
>
> http://interno.altervista.org/module...name=OraEsatta
>

Have you turned off the page cache on your web browser?
As if you have the page cache turned on, you will not reload the same
page source and restart the javascript, which will use the time set by
the php script

var Data_Inizio="October 6, 2007 13:38:42";

Maybe it's better you modify the javascript to use the client time
directly instead of letting the server set a time.

--

//Aho

not not.
the problem is not in the client but in the server.
the server turn 2 hour behind randomly.


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

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.

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.


Still, the best solution would be to not initialize the time based on the
servers clock, but on the clients clock.

--

//Aho

"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