Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 4
    that documentation tells you nothing - ok, it adds no functionality outside of generic functionality - ok, HOW?! establishes standardized names, HOW? Targets are more flexible... because of what? Magnets, how do they 3$^@% work?!? Commented Sep 1, 2020 at 17:48
  • The shorter summary is: socket must always exist. A socket starts the service (daemon) on-demand if it isn't already running. But you can mark both the socket and service as enabled in systemd to ensure that the daemon is loaded instantly at login without waiting for requests. On-demand loading is mostly useful for heavy service daemons that have long startup times. Commented Apr 25, 2021 at 18:59
  • 1
    +1 for link to "systemd for administrators".. so much depth of material to learn from. The blog has many more posts specific to systemd. Commented Jun 1, 2022 at 5:45