On Thu, 05.03.15 10:12, Alexander Larsson (al...@redhat.com) wrote:
See, even when the sleep command died the scope still exists, and is
even ACTIVE.
This appears to work fine here on git. There were some fixes to
systemd-run made, but it would be cool if you could verify that this
works for
On tor, 2015-03-05 at 00:00 +0100, Lennart Poettering wrote:
On Wed, 04.03.15 18:51, Alexander Larsson (al...@redhat.com) wrote:
If i run a transient scope on the user systemd instance like:
$ systemd-run --user --scope true
Then the scope seems to live past the end of the process.
On Thu, Mar 5, 2015 at 12:00 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 04.03.15 18:51, Alexander Larsson (al...@redhat.com) wrote:
If i run a transient scope on the user systemd instance like:
$ systemd-run --user --scope true
Then the scope seems to live past the end of
If i run a transient scope on the user systemd instance like:
$ systemd-run --user --scope true
Then the scope seems to live past the end of the process. Is there any
way to make it automatically go away with the last process in the
cgroup?
--
On Wed, 04.03.15 18:51, Alexander Larsson (al...@redhat.com) wrote:
If i run a transient scope on the user systemd instance like:
$ systemd-run --user --scope true
Then the scope seems to live past the end of the process. Is there any
way to make it automatically go away with the last
