3 ms·

It was done in Ubuntu a few versions ago. Afaik only the listening port config is ignored and instead is setup in systemd

• hsbauauvhabzb 1y ago
  Which is exactly the problem. It’s not obvious, is misleading and it’s cause is not easily determined just by looking at the config. What else is lurking that you and I aren’t aware of?
  • imoverclocked 1y ago
    > What else is lurking that you and I aren’t aware of? All of systemd... and network manager/modem manager/... I grew up with static configuration files, init scripts, inetd, etc... then grew into Solaris smf, dtrace, zones ... and then Linux implemented systemd. I really miss smf and related tools but systemd is still just meh to me. The implementation feels like a somewhat half-in-each-world brainchild.
  • tremon 1y ago
    The problem is that SSH is usually the admin interface to the system. You don't want unnecessary moving parts between you and your remote shell access when you need to troubleshoot a half-running system.
    • hsbauauvhabzb 1y ago
      I agree with everything but your indication that the problem is limited to only SSH.