Systemd help

[paequ2@lemmy.today]

TIL about user lingering. Interesting.

[kualk@lemm.ee]

Add to that need to use machinectl to establish normal user session with DBus in it.

[kualk@lemm.ee]

You don’t specify.

Do you use containers or not. It sounds like you are trying to start a rootless container.

Otherwise, you are over complicating things.

[kualk@lemm.ee]

I recommend that route as well.

Since you don’t know much, stick to native services. In most cases those are already preconfigured if native service package is available.

[innerscientist@lemmy.world]

Instead of using systemd user services you can just use a normal systemd service and tell it to run the command as a specific user, put something like this in a file at /etc/systemd/system/<unit Name>.service

[Unit]
Description=Run service as user test
After=network.target

[Service]
Type=simple
User=test
Group=test
ExecStart=/opt/teamspoke

[Install]
WantedBy=default.target

Then set it to start at boot

systemctl enable <unit Name>.service

And to start it now

systemctl start <unit Name>.service

[Guest]

Thanks to all who commented. You all helped. The problem was not listed here, but you helped me to find it. The issue is this: https://superuser.com/questions/1561076/systemctl-user-failed-to-connect-to-bus-no-such-file-or-directory-debian-9

[hendrik@palaver.p3x.de]

Nice that you were able to fix it. I think writing systemd unit files is a super useful skill. And systemd is a powerful tool. With the dozens of different things it can do and monitor for you.

I usually give each separate service its own user account. So teamspeak would get a teamspeak user and group and I'd write a system unit file to start it as User=teamspeak and Group=teamspeak. That's also what you'll find in most tutorials. But you can do it your way (as a user service), too. Whichever makes it easier to maintain and administer the stuff. I guess with the user sessions, you'd have to log in with that user(?) and the way I do it, everything runs completely unattended at system start and I never log in with those user accounts.

You don't need to write any Before= or After= directives, unless you want to set up or tear down some environment for these services. Maybe have a look at an example for a service file for teamspeak, the arch wiki says there is some example out there.

[digdilem@lemmy.ml]

Best answer.

Extra tip: You can combine the two last commands with: systemctl enable --now <unit name>.service

[monkdervierte@lemmy.ml]

Systemd help?

Run!

[drwho@beehaw.org]

I've run into this before. It's poorly documented but it usually means that you don't have the environment variable XDG_RUNTIME_DIR set in your shell. I fixed it by adding this to my ~/.bashrc file and making sure it gets loaded every time I fire one up: export XDG_RUNTIME_DIR=/run/user/$UID

Also, try running that command right before running systemctl --user...