Hello,
I still see weird behavior in the syslog (deb8.8): The first call of ntpdate
is before networking is done and ifup starts. The second and third call are
reasonable though.
Jun 8 13:30:28 magento systemd[1]: Starting system-ifup.slice.
Jun 8 13:30:28 magento systemd[1]: Created
Hi Kurt,
thanks for your response!
On 01/15/2017 06:25 PM, Kurt Roeckx wrote:
I don't think we should have a while loop in there, or at least time
out after some time.
Note that this is within a background sub-shell and that the
wait_for_file call above also contains a while loop. I do see
On Sun, Jan 15, 2017 at 05:49:51PM +0100, René Wagner wrote:
> tags 766838 + patch
> thanks
>
>
> Dear maintainers,
>
> my testing indicates that there are two distinct problems. First, for
> whatever reason, /etc/network/if-up.d/ntpdate is called with $IFACE = --all
> in addition to legitimate
tags 766838 + patch
thanks
Dear maintainers,
my testing indicates that there are two distinct problems. First, for
whatever reason, /etc/network/if-up.d/ntpdate is called with $IFACE =
--all in addition to legitimate interfaces. This causes a race
condition: If the $IFACE = --all instance
Package: ntpdate
Version: 1:4.2.6.p5+dfsg-3.1
Severity: normal
Lately, ntpdate has not been correcting the clock. But when I run
ntpdate-debian manually after the network is up, the clock is
correctly adjusted.
This is an excerpt from /var/log/demon.log:
4260 Oct 26 08:36:48 lenovo
On 26/10/14 08:53, Torquil Macdonald Sørensen wrote:
4264 Oct 26 08:36:48 lenovo ntpdate[371]: Can't find host ntp.uio.no: Name
or service not known (-2)
I recently noticed a similar problem caused by ntpdate being run before my
DNS server (maradns at the moment) is started. I've worked
6 matches
Mail list logo
