Package: sslh
Version: 1.15-1
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

I've just switched to systemd as init system on my box, and after rebbot
sslh wasn't running. From what I understand the cause of the failure is
a missing /var/run/sslh directory.

After adding the settings below to the sslh.service file, I can start it
manually using invoke-rc.d but it keeps failing at boot time:
ExecStartPre=/bin/mkdir -p /var/run/sslh
ExecStartPre=/bin/chown -R sslh:sslh /var/run/sslh/

Please let me know about any missing information in this report.

Thanks,

_g.

- -- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.12-1-486
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sslh depends on:
ii  adduser              3.113+nmu3
ii  debconf              1.5.52
ii  init-system-helpers  1.14
ii  libc6                2.17-97
ii  libconfig9           1.4.9-2
ii  lsb-base             4.1+Debian12
ii  update-inetd         4.43

Versions of packages sslh recommends:
ii  apache2                      2.4.7-1
ii  apache2-bin [httpd]          2.4.7-1
ii  openssh-server [ssh-server]  1:6.5p1-4

Versions of packages sslh suggests:
ii  openbsd-inetd [inet-superserver]  0.20091229-3

- -- Configuration Files:
/etc/default/sslh changed [not included]

- -- debconf information:
* sslh/inetd_or_standalone: standalone

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJTE6QAAAoJEO/obGx//s+DasMH/Ahstb84+phWURo5Bo6TbFbK
R9h2S0o3dNtW7izO5nRGNCN+Dm0efuCyEHRTZmCmBEUH0PRMDDdxWWx4fLENUZy3
VPjWm2s3498sjugaqy05ijTpfua19gYFqAUMArgR7R1C3n3RWmjVluXRnGbLy1it
FcJCWj72NmE0W+d8gb5kMLZJmP1e+96lBx4snTi3cNaHwD22ZWjbUnP81qhwJeat
ekQ90oz6goptGIr75TbU9ixprGBXLyaxHE2Q+zI2X3mJcjGXlMX3gYXsJCiZiUBV
EXMhCyUaMa4HlATIf00TgO112t1BPkPDzDXkSXs50DuKp19w40PzSYXVKUtYLkQ=
=8Imq
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to