this post was submitted on 13 Apr 2024
229 points (84.6% liked)

linuxmemes

21222 readers
93 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    229
    When people complain about systemd "violating the unix philosophy", this is what they actually mean (lemmy.world)
    submitted 7 months ago by [email protected] to c/[email protected]
    65 comments fedilink hide all child comments
     

    Credit for the answer used in the right panel: https://serverfault.com/a/841150

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 5 points 6 months ago* (last edited 6 months ago)

    pretty sure the runnit solution won’t allow this either

    I'm no expert, but I think you could make a special group, set the supervise directory to be owned by that group, and add all relevant users to that group? Either way, as I explained in a different reply, running the service as a user vs letting that user control a root service are completely different things, and one is not always a substitute for the other.