diff options
| author | Julio Capote <6135+capotej@users.noreply.github.com> | 2024-08-19 02:24:40 +0000 |
|---|---|---|
| committer | Julio Capote <6135+capotej@users.noreply.github.com> | 2024-08-19 02:24:40 +0000 |
| commit | 4a50857d70df9e17b0fe311c9aefbf847e26f47c (patch) | |
| tree | 03b713a93fd5d70b7504b458eca33be0759cab27 /content/blog | |
| parent | f61e4bf5692683039db019515159d598020cf1a8 (diff) | |
| download | capotej.com-master.tar.gz | |
Diffstat (limited to '')
| -rw-r--r-- | content/blog/2024-08-18-user-services-with-systemd.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/content/blog/2024-08-18-user-services-with-systemd.md b/content/blog/2024-08-18-user-services-with-systemd.md index 83d8bb1..b79c02b 100644 --- a/content/blog/2024-08-18-user-services-with-systemd.md +++ b/content/blog/2024-08-18-user-services-with-systemd.md @@ -9,9 +9,9 @@ tags = ["systemd","selfhosting"] Recently, I've started using `systemd` order to manage personal services on my servers. -Before that, I had either set up system-wide unit files or, for more ad-hoc services, started the process inside of a `screen` session, then detaching, hoping the process didn't crash overnight. +Before that, I had set up classic system-wide unit files or, for more ad-hoc services, started the process inside of a `screen` session, then detaching, hoping the process didn't crash overnight. -Using `systemd` instead is way better, since you get stuff like `journalctl` to view logs and `RestartAlways` keep things running after random crashes. Plus, all configuration lives in `$HOME` making it easy to edit and back up. +Using a user instance of `systemd` is way better, since you get stuff like `journalctl` to view logs and `RestartAlways` keep things running after random crashes. Plus, all configuration now lives in `$HOME` making it easy to edit and back up. In this post, I will show you how to set this up on any modern Debian-based system (or any distro that uses `systemd`, really). @@ -77,7 +77,7 @@ This starts `example` as soon as your copy `systemd` is launched (which should b ### Starting, Stopping and Status -You can now run the same `systemctl` commands you are used to, except they are run as your user (instead of root) and now require the `--user` argument: +You can now run the same `systemctl` commands you are used to, except they are run as your user (instead of `root`) and now require the `--user` argument: $ systemctl --user start example |