[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
[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.
[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 894b88a79421a89 0269e6c. scope. user-1000. slice sleep 1000 user-1000. slice sleep 1000 & 894b88a79421a89 0269e6c. scope
Running scope as unit run-r16d872f1b0
^Z
[3]+ Stopped systemd-run --scope --slice=
root:~# bg
[3]+ systemd-run --scope --slice=
root:~# systemctl show -p Slice run-r16d872f1b0
Slice=system.slice
[regression potential]
TBD
[scope]
this is needed only for Xenial.
this is fixed upstream by /github. com/systemd/ systemd/ pull/3094
https:/
which is included starting in v230, so is included in Bionic and later.