Opened 7 years ago

Last modified 4 years ago

#9108 new enhancement

ntpclient isn't started due to long init time needed by an umts dongle

Reported by: flux Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:


the hotplug event comes too early and at this time there is no stable connection to the internet although the interface is up. The workaround that works for me is to add a sleep before starting the ntpclient. Another workaround could be to start ntpclient anyway with the first server from the list. Another workaround that jow likes the most is to sleep several times in a loop

Attachments (1)

20-ntpclient.diff (443 bytes) - added by flux 7 years ago.
The diff is attached

Download all attachments as: .zip

Change History (3)

comment:1 Changed 7 years ago by flux

another possibility is to add a 5 sec sleep into the check_server() function in the /etc/hotplug.d/iface/20-ntpclient that is only called if ntpclient fails at the end. In this case there would be approximately 20 secs to iterate over all 4 servers

Changed 7 years ago by flux

The diff is attached

comment:2 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.