** Changed in: dhcp3 (Debian)
Status: New = Fix Released
--
Request ntp-servers by default
https://bugs.launchpad.net/bugs/74164
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing list
** Branch linked: lp:ubuntu/karmic/dhcp3
--
Request ntp-servers by default
https://bugs.launchpad.net/bugs/74164
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing list
** Bug watch added: Debian Bug tracker #407667
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407667
** Also affects: dhcp3 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407667
Importance: Unknown
Status: Unknown
--
Request ntp-servers by default
** Changed in: dhcp3 (Debian)
Status: Unknown = New
--
Request ntp-servers by default
https://bugs.launchpad.net/bugs/74164
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing list
Thanks, uploading now.
--
Request ntp-servers by default
https://bugs.launchpad.net/bugs/74164
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
This bug was fixed in the package dhcp3 - 3.1.1-5ubuntu8
---
dhcp3 (3.1.1-5ubuntu8) jaunty; urgency=low
* debian/dhclient.conf: Request ntp-servers by default (LP: #74164)
-- Jonathan Marsden jmars...@fastmail.fm Mon, 23 Mar 2009 19:42:32
-0700
** Changed in: dhcp3 (Ubuntu)
I can confirm this works as expected with the updated dhcpd3-common and
-client packages from Jonathan's PPA - the DHCP lease now has the 'ntp-
servers' option [1], consequently NTP has picked it up [2].
What else do we need to move this to the next step?
--- [1]
$ cat
You need sponsoring (see https://wiki.ubuntu.com/SponsorshipProcess)
All what's left here is to subscribe ubuntu-main-sponsors to attract
attention of a core-dev willing to sponsor that change. The debdiff
looks sane to me, but I can't sponsor it myself (yet).
** Changed in: dhcp3 (Ubuntu)
Re-testing this situation on jaunty alpha 6 in an enterprise environment
with a Microsoft DHCP server, it's still not addressed.
The situation is therefore, one of:
- NTP syncs to ntp.ubuntu.com and silently maintains a constant offset from
our local timeserver
- NTP tries to sync to
My solution for ntp-servers request from DHCP server (Ubuntu 8.04.1):
1) add 'ntp-servers' to the 'request' in /etc/dhcpd3/dhclient.conf;
2) change 'NTPDATE_USE_NTP_CONF=yes' to NTPDATE_USE_NTP_CONF=no in
/etc/default/ntpdate;
3) execute 'sudo ntpdate-debian' for testing.
--
Request
Without reference to any other comments/decisions on this bug...
It would clearly be more ideal to use 'ntp.ubuntu.com' rather than it's
IP address, but it is the lesser of the two evils
It would not be *more* ideal to use the hostname, it's the only sane
option. Using the IP address is simply
Indeed it is true - we don't need 'default ntp-servers xyz' in
/etc/dhcp3/dhclient.conf, since the defaults in /etc/ntp.conf will be
used, as /etc/ntp.conf.dhcp won't be created. That's half the changes
then...
--
Request ntp-servers by default
https://bugs.launchpad.net/bugs/74164
You received
Incidentally, we should be requesting 'nis-servers' too, in case that
needs to be configured for the environment, eg where on a different
network segment, thus broadcasting for it won't find it.
--
Request ntp-servers by default
https://bugs.launchpad.net/bugs/74164
You received this bug
The fix for this, and obvious intended behaviour is:
- add 'ntp-servers' to the 'request' directive in /etc/dhcpd3/dhclient.conf
- add 'default ntp-servers 91.189.94.4' (ntp.ubuntu.com) to
/etc/dhcpd3/dhclient.conf
I confirm that where the DHCP server doesn't pass the 'ntp-servers'
option,
14 matches
Mail list logo
