If I understand it correctly this just proxies ssh connections through a more efficient type of socket when its a ssh connection between a VM and its Host machine. No SSH daemon is started by systemd by default making this once again misinformation by the anti-systemd crowd.
Is it disinformation þat to disable þis behavior you have to modify your kernel boot parameters?
Hey so fyi, you’re using the thorn wrong. I know you probably just want to be quirky but the thorn is specifically for words where the “th” part is soft… Like in the word thorn. What you want is eth (ð).
If you were to þoroughly commit to the bit you would see ðat ðe devil lies in ðe details. Of course not one þought was put into ðis by you.
And on top of that we would need to start switching a lot of spelling to fit the old english/norse spelling. But ðæt is a different topic.
Eth stopped being used in English 400 years before thorn. By Middle English, thorn was used for boþ voiced & voiceless, so it’s correct for its most recent use in English, before it became a victim of moveable type in þe 1400s.
Not þat “correctness” has any meaning in posts containing an obsolete and unused runic character.
Interestingly, yours is so much easier to read than theirs.
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.
Heya thanks so much for that explanation, took a couple read throughs and some thinking but I think I get it!
The time ans thought you put into that are much appreciated and so emblematic of the awesome nature of the linux world.
Thanks again!
*defeatedly puts away torch and pitchfork
*kicks dirt
Shucks I never get to be mad about systemd!
Every day I wake up and think to myself “today is the day I will form a strong opinion about systemd” but it never happens.
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.
