clock synchronization with ntp server in Live CD
Derek Broughton
news at pointerstop.ca
Tue Jan 17 14:47:44 UTC 2006
Bob Nielsen wrote:
>
> On Jan 16, 2006, at 7:10 AM, Derek Broughton wrote:
>
>> 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)
I was aware of that. So, in this case the either apache2 install was not
using update-rc.d or update-rc.d was broken. Anyway, it was a long time
ago, and I need to check the situation again to see if a bug should be
filed.
> that handles the symlinks. From its man page:
>
> If any files /etc/rcrunlevel.d/[SK]??name already exist then
> update-rc.d does nothing. This is so that the system administrator
> can rearrange the links, provided that they leave at least one link
> remaining, without having their configuration overwritten.
This, however, somewhat contradicts your earlier statement. I'm a good boy,
I don't just delete symlinks in /etc/rc*.d/. I would have used
"update-rc.d -f ntpdate remove". Oops. Next update it would be back...
You have to just remove it in the default runlevel, which is rather
unintuitive.
--
derek
More information about the ubuntu-users
mailing list