submitted 8 months ago* (last edited 8 months ago) by to c/linuxmemes@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[–] 106 points 8 months ago* (last edited 8 months ago) (11 children)

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.

  • source
  • parent
  • hideshow 11 child comments
  • [–] 67 points 8 months ago (6 children)

    *defeatedly puts away torch and pitchfork

    *kicks dirt

    Shucks I never get to be mad about systemd!

  • source
  • parent
  • hideshow 6 child comments
  • [–] 4 points 8 months ago (3 children)

    It's upsetting for systemd users too, not having angry haters to go "See!?!!" back at.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 8 months ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 8 months ago (1 child)

    Any time I mess with init systems, I have to look up usage, no matter the system involved

    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 thing

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 8 months ago

    I do have some usage interaction, so ease of script writing is the most important for me.

    I've heard of runit.. ..one of the inits impressed me recently in regard to script writing - maybe what's used on OpenWRT. But, I don't remember if that was runit. You can tell how vested i am here. XD

  • source
  • parent
  • [–] 6 points 8 months ago

    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!

  • source
  • parent
  • [–] 0 points 8 months ago

    No, 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.

  • source
  • parent