SSH stands for Secure SHell and is a protocol to logon to a terminal shell via network.
You need to have an SSHd (or Secure SHell Daemon i.e a background service) running to accept and facilitate connections.
Systemd is a suite of services and tools that manage a Linux system, like a init system, service management, handing run levels, socket management, logging etc and gives the user tools like systemctl, journalctl, bootctl, basically anything ending with ctl is conventionally a systemd tool for users to manage their systems with.
Get it? Got it? Good.
systemd.autossh is an embedded ssh client in systemd that tries to help in reestablishing dropping connections. It does not actually start an SSHd (the actual service that facilitates connections) and is embedded for convenience to minimize frustrations with dropping connections.
I can’t believe you’re dissing systemd indirectly by dissing the reaction of systemd users to the reaction of the users that hate systemd.
To any neutral observers out there: See!?!! This is the kind of crap we get from the haters.
/s of course, I have no skin in this game. Any time I mess with init systems, I have to look up usage, no matter the system involved, and I haven’t run into anything too onerous.
You are talking about autossh, which is a completely different third-party SSH client tool that you have to install separately (as the link you shared describes) to have persistent SSH client connections and has nothing to do with systemd other than that you can start it as a systemd service (like any other third-party service).
OP is talking about systemd-ssh-generator, which is described here by Lennart Poettering (author of systemd) as working exactly as OP described it.
Given that it helps with ssh client connections and sshd is, basically, a server—yes. And even then, I imagine it doesn’t actually do anything if there’s no ssh connection.
I uhhh, just loaded Mint the other week. Any chance someone can English this for me?
Op is a bit confused, but here’s a primer first:
SSH stands for Secure SHell and is a protocol to logon to a terminal shell via network.
You need to have an SSHd (or Secure SHell Daemon i.e a background service) running to accept and facilitate connections.
Systemd is a suite of services and tools that manage a Linux system, like a init system, service management, handing run levels, socket management, logging etc and gives the user tools like systemctl, journalctl, bootctl, basically anything ending with ctl is conventionally a systemd tool for users to manage their systems with.
Get it? Got it? Good.
systemd.autossh is an embedded ssh client in systemd that tries to help in reestablishing dropping connections. It does not actually start an SSHd (the actual service that facilitates connections) and is embedded for convenience to minimize frustrations with dropping connections.
You can read about it here.
*defeatedly puts away torch and pitchfork
*kicks dirt
Shucks I never get to be mad about systemd!
Just be mad at systems the same way everyone else is; invent your own reality and throw a fit about that instead!
It’s upsetting for systemd users too, not having angry haters to go “See!?!!” back at.
I can’t believe you’re dissing systemd indirectly by dissing the reaction of systemd users to the reaction of the users that hate systemd.
To any neutral observers out there: See!?!! This is the kind of crap we get from the haters.
/s of course, I have no skin in this game. Any time I mess with init systems, I have to look up usage, no matter the system involved, and I haven’t run into anything too onerous.
Yeah. Just don’t interact with them often enough to remember and build muscle memory. Though, runit is very nice, very simple. E.g.
sv up thingNo, it seems you are a bit confused.
You are talking about autossh, which is a completely different third-party SSH client tool that you have to install separately (as the link you shared describes) to have persistent SSH client connections and has nothing to do with systemd other than that you can start it as a systemd service (like any other third-party service).
OP is talking about systemd-ssh-generator, which is described here by Lennart Poettering (author of systemd) as working exactly as OP described it.
So systemd.autossh is running even if sshd.service is disabled?
Given that it helps with ssh client connections and sshd is, basically, a server—yes. And even then, I imagine it doesn’t actually do anything if there’s no ssh connection.