Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25858 - [systemd] sshd.socket broken by systemd 35 update
Attached to Project:
Arch Linux
Opened by Marti (intgr) - Friday, 02 September 2011, 08:55 GMT
Last edited by Dave Reisner (falconindy) - Friday, 02 September 2011, 12:28 GMT
Opened by Marti (intgr) - Friday, 02 September 2011, 08:55 GMT
Last edited by Dave Reisner (falconindy) - Friday, 02 September 2011, 12:28 GMT
|
DetailsDescription: I'm using the sshd.socket unit from systemd-arch-units to launch my SSH server. However, starting with systemd update 35 I can no longer connect to it.
When I connect to it by netcat, I don't get the usual OpenSSH -- or any output at all. What's even more interesting, on every connection attempt I get this in my syslog, which is the SSH greeting string: Sep 2 11:39:37 arch sshd[10440]: SSH-2.0-OpenSSH_5.8 systemd is probably getting file descriptors mixed up. Instead of sending stdout to the socket, it sends it to syslog. This is almost certainly a result of the new systemd's default "StandardOutput=syslog" setting. |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 02 September 2011, 12:28 GMT
Reason for closing: Fixed
Additional comments about closing: community/systemd-arch-units 20110902
Friday, 02 September 2011, 12:28 GMT
Reason for closing: Fixed
Additional comments about closing: community/systemd-arch-units 20110902