Re: [systemd-devel] From command-line 'systemctl suspend' works' from cron it does not

[Kai Krakow]

Am Mon, 21 Mar 2016 09:21:39 +0100
schrieb Cecil Westerhof :

> 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?

It's probably because cron doesn't setup a systemd session. Do you
eventually run from a user crontab? Have you tried running from a root
crontab?

-- 
Regards,
Kai

Replies to list-only preferred.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Container IP resolution by name inside another container

[Jean-Sébastien Bour]

Le 13/03/2016 14:42, Jean-Sébastien Bour a écrit :

How can I have nss-mymachines (or whoever) resolve other containers'
names from inside a container ?


Hello,

has anyone an idea whether this (resolving a container's IP from its 
name, from inside another container, not only from the host)


* should work by default, and I should file a bug report,
* is doable when configured, but I must find documentation,
* is not yet implemented and I should file a feature request,
* will never happen and I must find another way (static addressing or 
whatever)?

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel