Comment # 23 on bug 926835 from Thomas Blume

(In reply to lynda t from comment #20)

> 	systemctl stop sshd.service
> 	systemctl disable sshd.service
> 	systemctl enable sshdgenkeys.service
> 	systemctl enable sshd@.service
> 	systemctl enable sshd.socket
> 	systemctl start sshd.socket
> 	systemctl start sshd.service
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Please don't do this, starting sshd.service conflicts with socket based
activation.
sshd.service should stay in state stopped and disabled.
After enabling socket based activation, sshd.service should look like this:

# systemctl status sshd.service
sshd.service - OpenSSH Daemon
   Loaded: loaded (/usr/lib/systemd/system/sshd.service; disabled)
   Active: inactive (dead)

and the status of the socket enabled service should show somehting like this:

# systemctl status sshd*
sshd@0-192.168.99.116:22-192.168.99.1:59126.service - SSH Per-Connection Server
(192.168.99.1:59126)
   Loaded: loaded (/etc/systemd/system/sshd@.service; static)
   Active: active (running) since Mi 2015-04-15 09:25:19 CEST; 16s ago
 Main PID: 1512 (sshd)
   CGroup:
/system.slice/system-sshd.slice/sshd@0-192.168.99.116:22-192.168.99.1:59126.service
           ��� 1512 sshd: root@pts/0
[...]