Re: enabling/disabling daemons
On Fri, Sep 27, 2002 at 07:35:47AM -0500, Graham Wilson wrote:
> On Mon, Sep 23, 2002 at 09:16:29PM -0400, Joey Hess wrote:
>> Noah L. Meyerhans wrote:
>>> When you install the ssh package, you are asked a debconf question "Do
>>> you want to run the ssh server?". If you say no, then a file
>>> /etc/ssh/sshd_not_to_be_run is created. The sshd init script checks for
>>> the existance of this file and does not start sshd if it exists.
>>> Postgresql also has this kind of functionality, but it's implemented
>>> completely different.
>> hmh has a point about invoke-rc.d making this unnecessary. Just want to
>> point out that we also have a /etc/default/ directory in policy now that
>> works similarly to the bsd one. While it's now sorta pointless to store
>> "don't evert start" info in there, it's still useful for other init
>> script configurations.
> what should ssh do then in its postinst file? first, it asks whether or
> not to start on boot, then what next?
Good question, fresh installation is easy: Call
"update-rc.d ssh stop 20 0 1 2 3 4 5 6 ." or
"update-rc.d ssh defaults", depending on the answer.
Upgrading OTOH is difficult because
update-rc.d -f ssh remove
update-rc.d -f ssh stop 20 0 1 2 3 4 5 6 .
is probably verboten.
You have to additionally get rid of all direct invocations of
/etc/init.d/ssh in the maintainerscripts, too.
cu andreas
Reply to: