On Fri, May 27, 2016 at 8:28 AM, Andrew Lutomirski <l...@mit.edu> wrote: > > Either the scope code is buggy or has IMO very strange behavior: > > $ systemd-run --user --scope echo foo > Running scope as unit run-4980.scope. > foo > > $ systemctl --user status run-4980.scope > ● run-4980.scope - /usr/bin/echo foo > Loaded: loaded (/run/user/1000/systemd/user/run-4980.scope; static; > vendor preset: enabled) > Drop-In: /run/user/1000/systemd/user/run-4980.scope.d > └─50-Description.conf > Active: active (running) since Fri 2016-05-27 08:16:03 PDT; 14s ago >
I played with this a bit. At least for now, I can get useful behavior like this: $ systemd-run --user --service-type=forking /bin/bash -c "/bin/sleep 20 &" Running as unit run-7737.service. The service will continue to exist until the whole process tree goes away. Shouldn't this be the *default* for --scope (and for tmux, screen, and nohup)? Also, ISTM someone (systemd?) should supply a really simple DSO that programs can use to indicate their desire to create a long-running process tree like this. -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
