Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 463974 - net-misc/ntp - ntp-client starts before network finishes authenticating
Summary: net-misc/ntp - ntp-client starts before network finishes authenticating
Status: RESOLVED DUPLICATE of bug 439564
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal with 2 votes (vote)
Assignee: Gentoo's Team for Core System packages
Depends on:
Reported: 2013-03-31 10:41 UTC by Ian Leonard
Modified: 2013-12-07 09:17 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Ian Leonard 2013-03-31 10:41:04 UTC
I am using ntp-client to set the system clock on a Raspberry Pi. The network connection is via wireless. The initscript for ntp-client starts before the network has finished authenticating with the access point (using wpa_supplicant). Changing the initscript for ntp-client to list "need net" instead of "after net" resolves this issue for me, as ntp-client then waits.

Reproducible: Always
Comment 1 josef.95 2013-10-02 14:23:07 UTC
This was probably already in fixed
Comment 2 Roland Ramthun 2013-10-27 11:51:41 UTC
This is an issue on all my systems which use NetworkManager. Having "after net" in the ntp-client init script makes ntp-client start immediatelly after NetworkManager has started, but before it established a network connection (authentication, DHCP, ...).

Consequently it fails due to DNS resolve errors or the like.

Changing the init script to "need net" makes ntp-client wait until the whole connection is established and solves this issue for me.

Please consider SpanKYs comment in and the obvious difference in behaviour between "need net" and "after net". I ask you to consider changing it back to "need net".
Comment 3 Gerald 2013-11-03 05:51:03 UTC
Same problem on my system after updating to newer hardware (not sure if the different network card has triggered it or the fact that the new system is just so much faster due to the ssd).

"need net" instead of "after net" solved it for me. Thanks for the hint!
Comment 4 Andrey Utkin 2013-11-04 09:54:50 UTC
"need net" instead of "after net" fixes it. Please fix it upstream.
Comment 5 SpanKY gentoo-dev 2013-12-07 09:17:56 UTC

*** This bug has been marked as a duplicate of bug 439564 ***