Regarding the choice between ntp and ntpdate, I suspect that ntpdate is
a smaller package then ntp. Even if configurable as client, ntp still
also is a server package. I do not know for sure but this might be the
reason behind the use of ntpdate.
To raise the sync frequency to several times a day
Workaround:
change the wait time from 10 seconds to 5 seconds:
/etc/init.d/sendsigs
[...]
# Kill all processes.
log_action_begin_msg Asking all remaining processes to terminate
killall5 -15 $OMITPIDS # SIGTERM
log_action_end_msg 0
alldead=
OMITPIDS0=$OMITPIDS
for seq in 1 2 3 4 5 ; do
I aggree this issue might be appropriate to be discussed at the mailing
list.
Also for this reason setting the but to incomplete
** Changed in: ntp (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Quote:
1. Where are you find a privacy issue? Please read the docu at
The issue is based in the name and origin of the target server. Calling
ntp.ubuntu cleary tells what kind of OS you are using.
This is an increasing issue today
2. The use of ntp.ubuntu.com is IMHO the availability of the
I agree.
Regarding the aspect that most systems will be booted only once a day or less
it will probably affect only a few people as it is.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
Public bug reported:
Currently ntpdate is started every time the network interface changes to up.
On systems that have a hardware clock this is not nessesary, causeing
unnessesary traffic and load on ntp servers.
If easily possible ntpdate shold rather be called daily or weekly via
cron, if
Public bug reported:
ntpdate calls a ubuntu specific ntp server on network-interface startup.
This causes some slight but unnessesary privacy issues as it identifies
the client software to anyone listening on the network.
This issue can be solved easily by adding the ubuntu/canonical ntp
