xenial: root@lp1881312-x:~# dpkg -l systemd|grep systemd ii systemd 229-4ubuntu21.28 amd64 system and service manager root@lp1881312-x:~# systemd-run --scope --slice=user-1000.slice sleep 1000 Running scope as unit run-rad93ed3206334259a90708def087987d.scope. ^Z [1]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root@lp1881312-x:~# bg [1]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root@lp1881312-x:~# systemctl show -p Slice run-rad93ed3206334259a90708def087987d.scope Slice=system.slice
root@lp1881312-x:~# dpkg -l systemd|grep systemd ii systemd 229-4ubuntu21.29 amd64 system and service manager root@lp1881312-x:~# systemd-run --scope --slice=user-1000.slice sleep 1000 Running scope as unit run-r4648aaa0fdca485b9b1a2b9a5298fb0f.scope. ^Z [2]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root@lp1881312-x:~# bg [2]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root@lp1881312-x:~# systemctl show -p Slice run-r4648aaa0fdca485b9b1a2b9a5298fb0f.scope Slice=user-1000.slice ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in 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 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [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] 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. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1881312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
