Place dunst.service in session.slice#1397
Conversation
By default, systemd would place it in `app.slice` which doesn't make sense; that's where apps go, not daemons that are part of the desktop session. `session.slice` makes a lot more sense for a daemon that's part of the desktop session.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1397 +/- ##
=======================================
Coverage 65.14% 65.14%
=======================================
Files 50 50
Lines 8651 8651
Branches 1022 1022
=======================================
Hits 5636 5636
Misses 3015 3015
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Could you link some docs about the slice option? I found this https://www.freedesktop.org/software/systemd/man/latest/systemd.slice.html where it says
Maybe I am misinterpreting this but shouldn't the service be added by default to system.slice? |
|
The upstream docs are confusing on this but this is a user service, not a system service. I could not find it documented but user services appear to be placed in app.slice by default. |
|
I found this https://www.freedesktop.org/software/systemd/man/latest/systemd.resource-control.html |
|
I have checked a systemd system and the session.slice is used for things like pulseaudio. which is fine for this pr. My only question at this moment is why is dbus in app.slice? |
|
It isn't for me. I use the dbus-broker implementation though: |
|
Well I will go ahed and merge then |
|
Thanks! |
By default, systemd would place it in
app.slicewhich doesn't make sense; that's where apps go, not daemons that are part of the desktop session.session.slicemakes a lot more sense for a daemon that's part of the desktop session.Related: flatpak/xdg-desktop-portal-gtk#504