Erik Thiele wrote: > the problem now is that the dhclient sets networking parameters after > ntpd has already started. dhclient won't restart ntpd because > configuration hasn't changed.
So what is the actual problem? ntp.conf.dhcp is not created, or it doesn't contain the right information, or ntpd is not restarted? > this way ntpd will fail on the ip > adress because the ethernet is down. Why would the ethernet be down after calling dhclient? An why is that ntpd's fault? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
