On Wed, Jun 1, 2016 at 2:19 PM, Przemek Klosowski < przemek.klosow...@nist.gov> wrote:
> On 05/27/2016 12:45 PM, Christopher wrote: > > > It seems to me that what's happening is that systemd is now enforcing this > "login session" perspective... metaphorically speaking, gluing the > transparent overlay onto the map (but don't worry! they also provide a > special adhesive remover!). This makes it that much harder for people to > make use of what's underneath without viewing it through the overlay... > which, as it turns out, is a *very* common thing to do (screen, tmux, > nohup, etc.). > > This is a very good observation. The 'login' infrastructure deals with > authorization to run processes on the computer, which is orthogonal to > managing characteristics of individual processes, such as whether they are > transient or persistent. Admitedly, the logout process has to deal with the > lingering processes: Windows, for instance, throws a dialog box asking to > terminate the apps. This is somehow a violation of layering which I just > pointed out above, but I think it is correct in asking for user intent. > > In any case, the common use case nowadays is a personal device, where this > whole issue is somehow moot: there are no multiple users, the user is the > administrator, and the login session is really from startup to > shutdown---so the proposed change doesn't change the user-visible behavior > much, except making the reboot quicker. > I think one needs to be careful with even this assumption though. I have used my server in a hybrid fashion, where I'll log into it both in a desktop environment and via SSH and use the same tmux window or backgrounded processes from each. Killing these processes just because I started them from the desktop instead of via SSH is not an agreeable default.
-- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
