On 06/01/2016 02:19 PM, Przemek Klosowski 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.
Actually, how does this proposal deal with network logins? If I SSH to another
system and run backup in the background, will it kill it when I log out?
That's too broad of a question. If the backup is provided by a service running
as a daemon on the system bus or as a system-wide systemd unit and all your
session is doing is telling it to start, it will continue to run.
If you have your user set to "linger", it will continue to run.
If you just have it running in the background, it would have died when you
logged out before this change (depending on shell behavior; some shells reparent
background tasks so it's ambiguous).
If you had it running under a 'screen' session, previously it would have kept
running, now it would exit.
So the "how" makes a big difference.