pool.ntp.org

[Darren Critchley]

Markus Kolb wrote:

> On 06.10.2004 13:00, Adam D. Barratt wrote:
>
>> On Wednesday, October 06, 2004 11:38 AM, Markus Kolb
>> <ubuntu-ml at tower-net.de> wrote:
>>
>>
>>> On 06.10.2004 05:04, Rob Weir wrote:
>>
>>
>> [...]
>>
>>>> When I boot offline, it fails very quickly; I think because I have no
>>>> available DNS servers so it just quickly fails to resolve.  If you
>>>> want to stop it from running at boot, run "rm /etc/rcS.d/S51ntpdate".
>>>
>>>
>>> The correct way would be
>>> $ sudo update-rc.d -f ntpdate remove
>>
>>
>>
>> No, no, no, no, no. :-) Sorry, but this is a common misconception.
>>
>> The above will work until the package is next upgraded, at which 
>> point the
>> symlinks will magically reappear when the maintainer scripts run
>> update-rc.d. The *correct* way is, as Rob said, to remove the symlinks.
>
>
> Yes, I know this but I don't see the link remove as the correct way. 
> It breaks the installation and you have to know and remember which 
> link and stuff you have removed by hand.
> I use a script with my changes which is excuted after each update and 
> it uses the Debian utilities to do this.
> If I don't run the script I have a system with defaults.
> Maybe in a year he wants the default ntpdate run on startup. Do he 
> remember that he has removed the link a year ago?
> I don't think so and maybe he will post here again why ntpdate doesn't 
> work...
>
> So I say removing init-links by hand is trash.

Why can't we have the ntp updates done by a crontab and maybe even find 
a nice front end that lets us set how often we want to go to 
pool.ntp.org rather than having it in the initscript at all?

Darren