On 27/05/16 15:48, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, May 27, 2016 at 03:26:45PM +0100, Tom Hughes wrote:
>
>> Which works fine except that the scope remains even after the screen
>> has exited...
>
> Hm, it shouldn't I think. Seems to work fine here. How
> are you running the command and what exactly remains behind?
So I'm trying this in F23 currently, so F24 might be different, but basically I
did:
systemd-run --scope --user /bin/screen
and got a scope like this:
% systemctl --user status run-17952.scope
● run-17952.scope - /bin/screen
Loaded: loaded (/run/user/2067/systemd/user/run-17952.scope; static; vendor
preset: enabled)
Drop-In: /run/user/2067/systemd/user/run-17952.scope.d
└─50-Description.conf
Active: active (running) since Fri 2016-05-27 16:01:41 BST; 33s ago
CGroup: /user.slice/user-2067.slice/user@2067.service/run-17952.scope
├─17952 /bin/screen
├─17953 /bin/SCREEN
└─17954 /bin/zsh
then hit ctrl-D to exit screen and was left with:
% systemctl --user status run-17952.scope
● run-17952.scope - /bin/screen
Loaded: loaded (/run/user/2067/systemd/user/run-17952.scope; static; vendor
preset: enabled)
Drop-In: /run/user/2067/systemd/user/run-17952.scope.d
└─50-Description.conf
Active: active (running) since Fri 2016-05-27 16:01:41 BST; 39s ago
Tom
--
Tom Hughes (t...@compton.nu)
http://compton.nu/
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
