You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2018. It is now read-only.
Yes but i would treat runtime units separatly altogether. Also keep in mind that I am only refering to system units. (user units are a whole different story)
So, i would associate a systemd_runtime_unit_t type with the units in /run/system/.*
because you cannot associate private types with runtime units, so all runtime units have the same type. (these runtime units have random unpredicable names)
So if you would label these with the normal generic unit type then, by allowing someone to start a runtime unit you will also allow that someone to start an ordinary generic unit , and that is probably something you might not want in the long run
The text was updated successfully, but these errors were encountered:
From @doverride:
The text was updated successfully, but these errors were encountered: