Bug#226349: ssh should not be started on upgrade if not running before

[Martin Godisch <martin@godisch.de>]

On Thu, Jan 22, 2004 at 01:18:52 +0100, Martin Godisch wrote:

> On Wed, Jan 21, 2004 at 01:17:37 +0000, Colin Watson wrote:
> 
> > Did you remove just one symlink, or all of them (which won't work)? I
> > just tried removing /etc/rc2.d/S20ssh and installing the package again,
> > and this was preserved. The package maintenance scripts seem to call
> > update-rc.d in the usual way.
> 
> I removed one of them and I believe the daemon was started on the
> upgrade. I'll watch it carefully next time and follow up to this
> bug or close it. Thanks!

I just reproduced the problem while upgrading mysql-server, which was
not running.

$ ls /etc/rc?.d/*mysql
/etc/rc0.d/K20mysql  /etc/rc3.d/S20mysql  /etc/rc5.d/S20mysql
/etc/rc1.d/K20mysql  /etc/rc4.d/S20mysql  /etc/rc6.d/K20mysql

This is runlevel 2, there is no startup link.

Setting up mysql-server (4.0.18-1) ...
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld.

Feel free to reassign this bug.

Kind regards,

Martin