Re: [users@httpd] Does Apache need to delay startup until system time set?

[Robert Moskowitz]

Yehuda,

thanks.  I already learned about chrony-wait for postfix.  I will apply 
it to httpd as well; Roundcubemail will need it...


On 04/20/2017 05:07 PM, Yehuda Katz wrote:
There are some parts of the HTTP conversation which could be affected 
by having the wrong time, but HTTPD itself doesn't care.
For example, if you are using cookies, caching, those could be 
affected by the time change (even more specifically, for PHP sessions, 
when the clock changes, the PHP session cleanup handler might think a 
session is very old and remove it).
If you want to wait for the time to be synchronized, I think you can 
change the systemd unit to require chrony-wait.service 
(https://git.tuxfamily.org/chrony/chrony.git/tree/examples/chrony-wait.service)


- Y

On Thu, Apr 20, 2017 at 4:57 PM, Robert Moskowitz > wrote:


This is for Centos7 on an armv7 SOC with no clock battery.

On startup, Centos runs Chronyd which eventually sets the system
clock.  This can happen really fast, or not depending.  I have
learned that it is NOT a good thing for postfix to start when the
system time is earlier than the build date of postfix.  There is a
way for me to delay postfix start until the time is set.

Does Apache also have this concern not to start until the time is
'fixed'?

thanks


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org

For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Does Apache need to delay startup until system time set?

[Yehuda Katz]

There are some parts of the HTTP conversation which could be affected by
having the wrong time, but HTTPD itself doesn't care.
For example, if you are using cookies, caching, those could be affected by
the time change (even more specifically, for PHP sessions, when the clock
changes, the PHP session cleanup handler might think a session is very old
and remove it).
If you want to wait for the time to be synchronized, I think you can change
the systemd unit to require chrony-wait.service (
https://git.tuxfamily.org/chrony/chrony.git/tree/examples/chrony-wait.service
)

- Y

On Thu, Apr 20, 2017 at 4:57 PM, Robert Moskowitz 
wrote:

> This is for Centos7 on an armv7 SOC with no clock battery.
>
> On startup, Centos runs Chronyd which eventually sets the system clock.
> This can happen really fast, or not depending.  I have learned that it is
> NOT a good thing for postfix to start when the system time is earlier than
> the build date of postfix.  There is a way for me to delay postfix start
> until the time is set.
>
> Does Apache also have this concern not to start until the time is 'fixed'?
>
> thanks
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>

[users@httpd] Does Apache need to delay startup until system time set?

[Robert Moskowitz]

This is for Centos7 on an armv7 SOC with no clock battery.

On startup, Centos runs Chronyd which eventually sets the system clock.  
This can happen really fast, or not depending.  I have learned that it 
is NOT a good thing for postfix to start when the system time is earlier 
than the build date of postfix.  There is a way for me to delay postfix 
start until the time is set.


Does Apache also have this concern not to start until the time is 'fixed'?

thanks


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org