So, my 2 cents... Some questions for upstream: * I assume killed processes are logged in the journal, but Is there any way to have a 'permissive' version? ie, simply log what would have been killed, but not do anything? That would be very helpful to folks to identify things that would be affected here without disrupting them at first. It would also allow bugs in other packages to get fixed up. * Does 'loginctl enable-linger <user>' take effect in the current session? Or do you have to start a new one? does it persist over sessions or only affects the current/next one? * How can I tell if linger is enabled or disabled on a user? * enable-linger/disable-linger need root? So, the only way the user can exclude things is to use systemd-run? For the Fedora side: I agree that it should be a F25 change so things can be coordinated and so it has higher visibility for users. This would also allow time/a chance for working groups to decide if they want to have a per edition default that's different from the base one. If something like a 'permissive' mode is possible, I would think it would be nice to move rawhide to that for now, if not, I don't feel too strongly either way on leaving it enabled for now. (On one hand disruption for users, on the other hand rawhide users should all be subscribed to this list and can change the default if they wish). If we can handle the common cases, I think this is a lovely step forward. kevin
Attachment:
pgp9gozaHsC02.pgp
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
