Bug#417118: ntpdate: Start sequence problem for some network setups

2007-07-03 Thread Simon Kelley
Touko Korpela wrote: Peter Eisentraut wrote: The network is started by /etc/rc0.d/S35networking, which starts ntpdate when eth0 becomes "up". At that time, the local nameserver is not yet available, it is started by /etc/rc[2345].d/S15bind9. ntpdate cannot resolve the names of the NTP servers a

Bug#417118: ntpdate: Start sequence problem for some network setups

2007-07-03 Thread Touko Korpela
Peter Eisentraut wrote: >> The network is started by /etc/rc0.d/S35networking, which starts ntpdate >> when eth0 becomes "up". At that time, the local nameserver is not yet >> available, it is started by /etc/rc[2345].d/S15bind9. ntpdate cannot >> resolve the names of the NTP servers and fails. >

Bug#417118: [pkg-ntp-maintainers] Bug#417118: ntpdate: Start sequence problem for some network setups

2007-04-03 Thread Peter Eisentraut
Am Sonntag, 1. April 2007 18:13 schrieb Lupe Christoph: > The network is started by /etc/rc0.d/S35networking, which starts ntpdate > when eth0 becomes "up". At that time, the local nameserver is not yet > available, it is started by /etc/rc[2345].d/S15bind9. ntpdate cannot > resolve the names of th

Bug#417118: ntpdate: Start sequence problem for some network setups

2007-04-01 Thread Lupe Christoph
Package: ntpdate Version: 1:4.2.2.p4+dfsg-2 Severity: normal ntpdate is started whenever a network interface becomes "up". The start script is /etc/network/if-up.d/ntpdate. Now imagine this scenario: you have a machine attached to a LAN. This machine uses a static IP address (i.e. no PPP, no DHCP