clock synchronization with ntp server in Live CD

Bob Nielsen nielsen at
Mon Jan 16 18:36:32 UTC 2006

On Jan 16, 2006, at 7:10 AM, Derek Broughton wrote:

> Bob Nielsen wrote:
>> On Jan 14, 2006, at 8:23 AM, Derek Broughton wrote:
>>> Sure, and you could just remove /etc/init.d/ntpdate, but the next  
>>> time
>>> ntpdate got updated through apt it would put it back, along with
>>> all the init links.
>>> It's one of the problems I've noted with Debian distros and sysv
>>> for years,
>>> and I still can't see a good way to fix it.  We need some way to be
>>> able to
>>> override the init scripts that run at boot time that will survive
>>> through
>>> updatess.
>> If you remove the symbolic link /etc/rc2.d/ntpdate, the other (rc3,
>> rc4, etc.) links will remain and if ntpdate is updated the link will
>> not be recreated.
> oops.  You may well be right.  I shouldn't have generalized.  Apache2
> _definitely_ used to recreate symlinks.  I wanted to move it to  
> starting
> after kdm - since I only use a web server on my laptop for my own
> development, I don't need to wait for the server to start before  
> logging
> in.  However, next time apache2 was upgraded it simply made a second
> symlink to the init script, and caused errors in the boot sequence.  I
> shouldn't have assumed, though, that that's the way _all_ init  
> scripts get
> installed.
> Now that I know it doesn't _have_ to be that way, I should check  
> whether it
> still happens with apache, and if it does I'll file a bug.  Thanks

Actually it is update-rc.d (which is run by the postinstall scripts)  
that handles the symlinks.  From its man page:

     If  any  files  /etc/rcrunlevel.d/[SK]??name already exist then  
        rc.d does nothing.  This is so that the system administrator  
can  rear‐
        range  the links, provided that they leave at least one link  
        without having their configuration overwritten.


More information about the ubuntu-users mailing list