[Pkg-systemd-maintainers] systemd support in openssh-server

[Russ Allbery]

Colin Watson <cjwatson at debian.org> writes:
> On Wed, Feb 12, 2014 at 02:48:59AM +0200, Uoti Urpala wrote:

>> I think you've misunderstood something about how systemd sysvinit
>> compatibility works. SSH started through the compatibility layer DOES
>> count as active, and is "under systemd control" - which is why for
>> example dependencies between init scripts and native units work fine,
>> unlike under upstart, as mentioned in the CTTE discussion. That's what
>> I meant by the "inconsistent state" above.

> Aha, I see.  Just inverting the check wouldn't be the right fix, IMO,
> but I'll retest this and sort out a proper fix.  Thanks for the
> clarification.

Is it as simple as just stopping and starting sshd once the systemd unit
file is installed and systemd has been reloaded?  Does systemd remember
that the service was started via an init script so that it will stop via
the init script and then start via the unit?

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>