2016-04-01 21:34 GMT+02:00 Lennart Poettering <lenn...@poettering.net>:
> On Mon, 21.03.16 09:21, Cecil Westerhof (cldwester...@gmail.com) wrote:
>
> > When executing
> > systemctl suspend || echo "Error code: ${?}"
> > from the command-line it outputs
> > Error code: 1
> > and it puts my machine in suspend.
> >
> > When putting it in cron it gives the following errors:
> > Failed to execute operation: Access denied
> > Failed to start suspend.target: Access denied
> > and gives the output:
> > Error code: 4
> >
> > What is happening here? Is it possible to run 'systemctl suspend' from
> > cron, or is there a reason why this is not possible?
>
> if you run "systemctl suspend" as unprivileged user, PolicyKit is
> queried whether your user shall be allowed the opreatoin. The default
> policy for PolicyKit we install says that users on local consoles may
> suspend the system. However, a cron user is not on a local console,
> hence doesn't get this privilege.
>
OK, thanks. I solved it by using sudo.
--
Cecil Westerhof
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
