https://bugzilla.novell.com/show_bug.cgi?id=359502 Summary: ntpdate call without timeout setting stalls bootup when network down Product: openSUSE 10.3 Version: Final Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jo@feuersee.de QAContact: qa@suse.de Found By: --- When ntp is configured to query timeservers via ntpdate on startup, this can result in a very long bootup sequence if the timeserver(s) can't be reached (due to network down/timeserver moved/whatever). Problem is that in /etc/init.d/ntp the call to $NTPDATE_BIN is done without the -t (timeout) option. If -t is omitted, the default is used, which AFAICS is 1800s. Thus, ntp stalls the bootup for 30min per timeserver which isn't really useful. IMHO the best solution would be a new config option in /etc/sysconfig/ntp ## Type: integer ## Default: 30 # # Timeout for ntpdate # NTPD_INITIAL_TIMEOUT=30 and using this value in /etc/init.d/ntp when calling ntpdate -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.