News for hackers. Stuff that matters.
Re:Show HN: Interactive systemd (a better way to work with s... by greenavocado on Saturday January 18, 2025 @01:58PM (#42750493)
This is why I have instated a policy of using systemd --user services whenever possible.

If you don't need elevated permissions this is ideal.

All you have to do is enable linger using loginctl if you want your service to auto start as the user on boot unattended.

Your user services live in ~/.config/systemd/user

Re:Show HN: Interactive systemd (a better way to work with s... by bityard on Saturday January 18, 2025 @04:46PM (#42751663)
I used to do this but frankly it's easier to run a system-level unit as whatever user you want and keep all the files in /etc instead of scattered around /home.

The user-level units are most useful when running an actual multi-user system. If you trust your users to not abuse them, anyway.

Re:Show HN: Interactive systemd (a better way to work with s... by j16sdiz on Saturday January 18, 2025 @07:09PM (#42752493)
I tried, but found it very confusing around the user session. Apparently an environment variable need to point to a started dbus. I can't get consistent results over local session vs ssh vs su vs sudo
Re:Show HN: Interactive systemd (a better way to work with s... by greenavocado on Tuesday January 21, 2025 @03:59PM (#42785124)
What are you trying to do with dbus?