3 ms·

Indeed. It has to be completely removed from the system and even then there is no guarantee it won't be brought back by some minor update in a couple of days. T

Indeed. It has to be completely removed from the system and even then there is no guarantee it won't be brought back by some minor update in a couple of days. This is why I had to chattr +x in Ubuntu 22 and older. Not anymore in 24, but we'll see.

vetinari 2y ago
resolv.conf is an internal implementation detail of glibc. You are not supposed to touch it. Congratulation to breaking your system.
jauntywundrkind 2y ago
Wrong and wrong. It just needs to be stopped. And you can mask it to make sure it never ever ever is started by anyone again. C'mon man, 0 for 0 so far on your grumbles.
- egorfine 2y ago
  It absolutely wasn't enough to stop and mask it under ubuntu 22.04.
  - jauntywundrkind 2y ago
    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.
    - egorfine 2y ago
      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.
    - vetinari 2y ago
      `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]
      - egorfine 2y ago
        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.

vetinari 2y ago

resolv.conf is an internal implementation detail of glibc. You are not supposed to touch it. Congratulation to breaking your system.

jauntywundrkind 2y ago

Wrong and wrong. It just needs to be stopped. And you can mask it to make sure it never ever ever is started by anyone again. C'mon man, 0 for 0 so far on your grumbles.

egorfine 2y ago
It absolutely wasn't enough to stop and mask it under ubuntu 22.04.
- jauntywundrkind 2y ago
  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.
  - egorfine 2y ago
    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.
  - vetinari 2y ago
    `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]
    - egorfine 2y ago
      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.