Hacker News new | past | comments | ask | show | jobs | submit login

It absolutely wasn't enough to stop and mask it under ubuntu 22.04.





Do you know how to use netstat to see who is holding the port open? This seems like a major Problem Exists Between Keyboard And Chair issue. But also Ubuntu can be a special place. But if you stop the service & the port is still open... It's probably not that service, it's something else, and so throwing shade at systemd is again not accurate.

Ah. It might be a systemd-resolved.socket (or similarly named), allow socket activation. Systemd would warn you when you disable the service that it wouldn't be giving up the socket, that it could still be restarted. Because it's a great monorepo that's smart & courteous.


I think we're confusing two things here. ssh via socket activation is of course a brain damage done solely by Ubuntu. But systemd goes a long way to make sure it hurts, because `ps ax | grep sshd` will definitely show you that /usr/bin/sshd is running. Except it's not it. But maybe that's Ubuntu thing as well, not sure here.

`sudo netstat -nlp` or `sudo ss -nlp` (without root you won't know pid).

`systemctl status ssh` shows, that it is socket-activated:

    TriggeredBy: ● ssh.socket
[Oh, checking the entire thread for context; never mind]

Hindsight.

You would know to run netstat or lsof if you have expected something like that to happen. It certainly wouldn't ever cross my mind to have sshd socket-activated and systemd actively trying to hide the fact. This change by Canonical was out of the blue, totally unexpected.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: