[systemd-devel] some services always being killed when stress tests running

Hi, We are running some stress tests as a systemd service by using STAF: % sudo systemctl status staf.service ● staf.service - Start staf after boot Loaded: loaded (/etc/systemd/system/staf.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2016-03-21

Re: [systemd-devel] Suspend does not work from a service

2016-03-21 10:34 GMT+01:00 Colin Guthrie : > Cecil Westerhof wrote on 19/03/16 23:54: > > 2016-03-18 17:16 GMT+01:00 Cecil Westerhof > >: > > > > I wrote as script to put my netbook into suspend when it is locked > >

[systemd-devel] systemd efi boot and default entry

I'm happy with systemd and its efi loader support. Now i want to have two entries and assign priority to it via systemd, in my use-case i want to know last succeseful boot entry and use it. After upgrade i want to boot from new antry and if it fails - change priority to lower level... Does it

[systemd-devel] ExecStop upon un-expected but clean shutdown

Hi, I have a daemon that is socket-activated through a systemd-managed localhost TCP socket. The daemon is normally shutdown by a simple systemctl stop with ExecStop=curl -X POST on the right HTTP endpoint which makes it easy to cleanup resources and make sure my data hits the hard disk. Now, it

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

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