brozek/website
1
0
Fork 0
mirror of https://github.com/Brandon-Rozek/website.git synced 2025-10-10 06:51:13 +00:00
Code Issues Projects Releases Packages Activity

Added medium syndication metadata

Browse source
This commit is contained in:
Brandon Rozek 2023-02-18 13:12:02 -05:00
parent 79329aae66
commit 387dd491b1
No known key found for this signature in database
GPG key ID: 26E457DA82C9F480
30 changed files with 175 additions and 134 deletions
Download patch file Download diff file Expand all files Collapse all files

10
content/blog/non-root-systemd-scripts.md
View file

@ -1,10 +1,12 @@
---
title: "Non-Root Systemd Scripts"
date: 2022-03-15T23:55:19-04:00
date: 2022-03-15 23:55:19-04:00
draft: false
tags: ["Linux"]
math: false
medium_enabled: true
medium_post_id: f527d0f12fb8
tags:
- Linux
title: Non-Root Systemd Scripts
---
I know of two ways to run systemd services not as root. They both have their pros and cons associated with them.
@ -105,4 +107,4 @@ From [FreeDesktop](https://www.freedesktop.org/software/systemd/man/loginctl.htm
For a multi-user system, one can argue that linger is not a good property to have because users can then have a lot of processes spawned and persistent even if they are not using the system. In that case, having an admin individually add systemd unit files using the first approach makes sense.
The second approach has the benefit that the admin only has to set the linger property of the user once, and then the user can create as many systemd unit services as they'd like.
The second approach has the benefit that the admin only has to set the linger property of the user once, and then the user can create as many systemd unit services as they'd like.