On Tue, May 31, 2016 at 03:04:52PM -0600, Orion Poplawski wrote: > On 05/29/2016 05:14 PM, Chris Murphy wrote: > > On Fri, May 27, 2016 at 5:03 PM, Paul Wouters <p...@nohats.ca> wrote: > > > >> If there is a systematic > >> problem of badly written code leaving orphaned code running when > >> a user logs out, then that broken code should be fixed instead of > >> adding another layer of process management. systemd is not capable > >> of interpreting the user's intent. > > > > That isn't working. Users are constantly running into restart and > > shutdown delays. Troubleshooting this to find out what process is > > holding things up is totally non-obvious. Identifying the process is > > half the problem, and then getting it fixed and released to Fedora can > > be months, by which time some other process is affected. > > But the delays in system shutdown/restart were introduced by systemd in the > first place. I would argue that these delays are much too long.
Set DefaultTimeoutStartSec= in /etc/systemd/systemd.conf. The default default has to be fairly high because of the wide range of hardware that people are using (e.g. a 10 year old uni-processor machine swapping to a slow rotational disk). Zbyszek -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
