In article [EMAIL PROTECTED],
Phil Dyer [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Miquel van Smoorenburg said:
If you want to keep updates from starting the daemon, just chmod 644 it.
That sounds reasonable...and simple. :) thanks.
Reasonable, simple, and wrong :)
As
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Miquel van Smoorenburg said:
OK, although both solutions work, (I guess - I haven't tried the second
solution) it still seems kludgy to me. If I use the debian supplied tool
to remove a service from startup _totally_, and I use a debian supplied
tool
Phil Dyer wrote:
Nope. Because that is not how it works or has ever worked. Your
expectation is skewed from reality (sorry).
Hate to keep beating this. But my response is:
Just because it's not how it's ever worked doesn't mean it's right. Can
you give me reasoning as to *why* it works like
/phil writes:
It does... what? If it checked to see if I've turned off a service...
It won't restart the service if you have left at least one K link in place.
Debian provides several tools for turning services on and off. My favorite
is sysvconfig (since I wrote it).
--
John Hasler
--
To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Hasler said:
It won't restart the service if you have left at least one K link in place.
Debian provides several tools for turning services on and off. My favorite
is sysvconfig (since I wrote it).
thanks, John. I'm checking out sysvconfig
In article [EMAIL PROTECTED],
Phil Dyer [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Clymer wrote:
The debian post install script probably doest go through the rc.*
directories looking for runlevel entries since these are all just
symlinks to a script in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Miquel van Smoorenburg said:
If you want to keep updates from starting the daemon, just chmod 644 it.
That sounds reasonable...and simple. :) thanks.
Reasonable, simple, and wrong :)
As long as one start or stop link is still present,
7 matches
Mail list logo
