On 4/11/2019 8:32 AM, Przemek Klosowski wrote:
On 4/11/19 10:16 AM, Lennart Poettering wrote:
However, that's intended for system services only (i.e. for services
running as users UID < 1000). For regular users (i.e. human ones,
those with UID >= 1000), the idea is to install timer units in the
per-user instance of the systemd service manager instead. That service
manager runs inside a PAM session of the user, and the lifetime is
normally bound to the time the user is logged in, meaning that users
who are not logged in cannot run stuff. (however, specific users can
be marked as "lingering" though a privileged operation and if so
their specific service manager is started at boot and stays around
until shutdown, so that their timers can run outside of the immediate
login time of the user).
I think you're saying that systemd is designed on an assumption that
such jobs are part of system operation, and will have to run as
system/privileged jobs or at least be designated as 'lingering', which
you say requires system privilege. I would argue that on my own system
(which is a majority of systems now) it should be easy to designate
low-privilege jobs as lingering: I should get to decide if it's useful
for them to run even if I don't have a current login session.
While we're discussing session-tying for cron-esque background
automation, it would be nice to have a resolution for
https://bugzilla.redhat.com/show_bug.cgi?id=911766
via https://bugzilla.redhat.com/show_bug.cgi?id=995792#c16
It's unfortunate that it still fills up basic syslog with it:
https://access.redhat.com/solutions/1564823
-jc
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
