1
ntp (1:4.2.0a-6) unstable; urgency=low
3
The "noserve" configuration option was buggy in versions before 1:4.2.
4
It did not restrict everything it was documented to restrict.
6
The impact on existing configuration files is that if you have "noserve" in
7
your /etc/ntp.conf, and you can no longer sync to your peers, you might
8
need to replace the "noserve" option with "noquery" or "nomodify".
10
-- Matthias Urlichs <smurf@debian.org> Mon, 29 Mar 2004 20:21:30 +0200
12
ntp (1:4.2.0a-3) unstable; urgency=medium
14
Downgrading the NTP package will not work automatically because the init
15
scripts have changed significantly.
17
The old init scripts and cron.daily/weekly files for ntp-simple and
18
ntp-refclock have been saved+disabled by renaming them to
19
"NAME.dpkg-old". If you have made any changes to them, you need to port
20
these changes to the new /etc/{init.d,cron.daily,cron.weekly}/ntp-server
23
-- Matthias Urlichs <smurf@debian.org> Sat, 20 Mar 2004 09:13:51 +0100
25
ntp (1:4.2.0a-0.1) experimental; urgency=low
27
Upstream has implemented their own patch for chroot-jail and change-uid.
28
Predictably, they use different flags (-j and -u, not -R and -U).
30
The Debian patch introduced in version 1:4.2.0-0.4 is therefore removed;
31
-R and -U are no longer recognized.
33
-- Matthias Urlichs <smurf@debian.org> Tue, 2 Mar 2004 11:44:40 +0100
35
ntp (1:4.2.0-0.6) experimental; urgency=low
37
The common parts of the "simple" and "refclock" NTP server packages have
38
been split off into their own package "ntp-server".
40
"ntp-server" now contains the code which needs to run on the same system
41
as the NTP server (example: startup scripts).
43
"ntp" consists of those programs which access an NTP server either locally
44
or across the Internet.
46
-- Matthias Urlichs <smurf@debian.org> Tue, 3 Feb 2004 17:18:40 +0100
48
ntp (1:4.2.0-0.3) unstable; urgency=low
50
/etc/ntp.conf and /etc/default/ntp are no longer generated by the
51
postinst scripts. Instead, they're now regular conffiles. You will
52
therefore see a standard "Update?" message from dpkg.
53
You should answer "Y" if you did not modify your NTP configuration
56
The default NTP time server is "pool.ntp.org", which resolves to a
57
list of public stratum-1 and stratum-2 servers. One of them will be
58
picked semi-randomly each time your NTP server starts.
60
Note that the default configuration does NOT send broadcasts and does NOT
61
allow any remote queries.
63
"Remote" is defined as non-RFC1918 network addresses, i.e. anything
64
not in 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16. The ntp server
65
does not try to discover any interface addresses. This is a feature.
67
-- Matthias Urlichs <smurf@debian.org> Tue, 23 Dec 2003 19:55:23 +0100
added
removed
debian/NEWS.Debian
