** Description changed: [impact] running 'systemd-run --scope --slice=$SLICE $PROGRAM' does not start the program under $SLICE, instead it starts it under system.slice [test case] root:~# systemd-run --scope --slice=user-1000.slice sleep 1000 Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope. ^Z [3]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root:~# bg [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope Slice=system.slice [regression potential] - TBD + This defers running the manager unit load queue when setting the slice + for a transient unit, as well as actually passing the slice parameter + over the bus when using --scope, so any regression would very likely + involve incorrectly setting the slice for a scope and/or problems when + processing transient units that specify a slice. [scope] this is needed only for Xenial. this is fixed upstream by https://github.com/systemd/systemd/pull/3094 which is included starting in v230, so is included in Bionic and later.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881312 Title: systemd-run does not make the new scope unit part of the slice specified via the --slice arg To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1881312/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
