On Mon, 08 Mar 2004, Thomas Hood wrote: > On Mon, 2004-03-08 at 09:16, Henrique de Moraes Holschuh wrote: > > In fact, currently invoke-rc.d will refuse > > to start/restart the service > > Actually this is not true.
Indeed it is not. Answering such mails late at night is not wise, and I should have waited till morning. 1. Invoke-rc.d currently does not bother with no symlinks at all, it will tolerate that. I am not sure this is how I wrote it initially, and I do think this is a small bug anyway. But that's a step ahead for "no-op" operation. 2. If no information exists for the current runlevel (no symlink), invoke-rc.d will allow anything to happen [in the absence of policy-rc.d]. This is just as bad for "no-op" as my mistaken interpretation of the invoke-rc.d code in the last email. > However, this just reinforces your main point. Thanks. At least I did not make a complete fool of myself, yet. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
