you are viewing a single comment's thread
view the rest of the comments
[–] 52 points 8 months ago (9 children)

It uses a completely different paradigm of process chaining and management than POSIX and the underlying Unix architecture.

That’s not to say it’s bad, just a different design. It’s actually very similar to what Apple did with OS X.

On the plus side, it’s much easier to understand from a security model perspective, but it breaks some of the underlying assumptions about how scheduling and running processes works on Linux.

So: more elegant in itself, but an ugly wart on the overall systems architecture design.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 24 points 8 months ago (7 children)

    It uses a completely different paradigm of process chaining and management than POSIX and the underlying Unix architecture.

    I think that's exactly it for most people. The socket, mount, timer unit files; the path/socket activations; the After=, Wants=, Requires= dependency graph, and the overall architecture as a more unified 'event' manager are what feels really different than most everything else in the Linux world.

    That coupled with the ini-style VerboseConfigurationNamesForThatOneThing and the binary journals made me choose a non-systemd distro for personal use - where I can tinker around and it all feels nice and unix-y. On the other hand I am really thankful to have systemd in the server space and for professional work.

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

    I'm not great at any init things, but systemd has made my home server stuff relatively seamless. I have two NASs that I mount, and my server starts up WAY faster than both of them, and I (stupidly) have one mount within the other. So I set requirements that nasB doesn't mount until nasA has, then docker doesn't start until after nasB is mounted. Works way better than going in after 5 minutes and remounting and restarting.

    Of course, I did just double my previous storage on A, so I could migrate all of Bs stuff back. But that would require a small amount of effort.

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

    what do you use as a prerequisite for the nas A mount? or does it iust keep trying in a loop?

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

    I have a wait-for-ping service that pings nas A, once it gets a successful response it tries to mount.

    I lifted it from a time when I needed to ping my router because Debian had a network-online service bug. I adapted it to my nas because the network-online issue eventually got fixed and mounting my shares became the next biggest issue.

    It seems like this person might have grabbed that same fix for what I eventually did because our files are...oddly almost exactly the same.

    https://cweiske.de/tagebuch/systemd-wait-nfs.htm

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

    thanks!

    do you perhaps also have a solution for hanging accesses to network mounts when the server is inaccessible?

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

    Do you mean a hang on boot when trying to mount? For that I use the nofail option in fstab. I also use the x-systemd.automount option so if something is not mounted for whatever reason, it tries to mount it when something attempts to access it.

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

    no, I mean the system has been up for a long time, but the server went down, and connection was lost

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

    That's all handled with adding the x-systemd.automount option to my fstab entry. If it disconnects it's unmounted, when it's available again it mounts when something tries to access it.

    I have occasionally needed to restart some services if they didn't like getting disconnected, but as far as mounting goes it's handled pretty smoothly with that option.

  • source
  • parent