I could use some help. I’m a pretty noobish linux user and have a linux server (running headless ubuntu). I use it for basic provisions of computer services, and to learn.

For the most part I’ve been able to stumble through the tasks I want to take on. One of the programs my server runs is Teamspeak, and it is always running. When i reboot the server, it’s the first thing I fire back up. I’ve been aware of systemd for some time now and this has been a prime candidate, but I’ve been putting off setting up any services. I figured the time has come. Holy crap, what a vortex systemd has proven to be.

When I built my server I read that it’s good practice to run the software that users will be connecting to through a non-admin account, so I did that. I have a non-admin account that I tmux my various server software on manually.

Reading some systemd tutorials, I’ve built a service file and I’m trying to register it on my non-admin account, but I get an error when I try to run systemctl --user daemon-reload: “Failed to connect to bus: No medium found”. I do not get this error when I run it on the admin account.

All the documentation I can find has got my head spinning. I’m pretty sure you need a doctorate in comp sci to understand the various man pages and webpages.

I mean hi there: https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#Options

Like holy fsck: https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html

I think the real question that I’m looking for is if I should be configuring services to run through my admin account, configuring services with my admin account to run as a specific user, or configuring services through my specific user account?

Also, something like Teamspeak, which just needs to run when the server is up and running, does it need before and after definitions, or if I omit them will that work fine?

Any tips, tricks or tutorials are appreciated!

  • InnerScientist@lemmy.world
    27·
    2 days ago

    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
    • DigitalDilemma@lemmy.mlEnglish
      11·
      2 days ago

      Best answer.

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

  • hendrik@palaver.p3x.deEnglish
    51·
    2 days ago

    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. I don’t use it myself, as it’s not Free Software, but good luck convincing your friends to switch to Mumble😅

  • liliumstar@lemmy.dbzer0.comEnglish
    3·
    2 days ago

    I think that error is related to a missing dbus session but don’t quote me on that.

    You will probably find it easier to use a system level service, but run it as your unprivileged user with User= and Group= directives. Once you get that working, there are various other parameters you can add to harden the service if you like.

    This is a good reference for hardening: https://docs.arbitrary.ch/security/systemd.html

    The arch wiki has a good general reference for all things systemd: https://wiki.archlinux.org/title/Systemd

    • Kualk@lemm.ee
      2·
      2 days ago

      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.

    • Kualk@lemm.ee
      11·
      2 days ago

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

      But that only makes sense for rootless containers. User management in rootless container and users in roootful containers can get complicated fast and depends on how image is built.

  • Kualk@lemm.ee
    1·
    2 days ago

    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.