Tweet
Originally posted by sarfarazahmad
View Post
-
I would like to see these timeouts be configurable to desired values and using 0 for disabling timeout entirely. And when there is a stuck process at shutdown time, systemd should write an entry in the log mentioning what programs/processes are still running at that point so that can help with debugging (or filing bug reports against such misbehaving applications). -
-
so much silly people are still thinking it is a bug with systemdOriginally posted by sarfarazahmad View PostComment
-
if you have such stupid requirement, change timeout in config file ffsOriginally posted by sarfarazahmad View PostComment
-
-
1615 is not closed, but its sister-bug IS declared closed. Lennart is asking anyone who was hit by this bug to test systemd 230 whenever possible and report back.Originally posted by ihatemichael View PostLast edited by Ericg; 22 May 2016, 01:03 PM. Reason: Replaced "fixed" with "closed" to avoid confusing.All opinions are my own not those of my employer if you know who they are.Comment
-
Gotcha. Still waiting for 230 to hit [core] on Arch and I'll test it out.Originally posted by Ericg View PostComment
-
Sister-bug is https://github.com/systemd/systemd/issues/2691Originally posted by ihatemichael View PostAll opinions are my own not those of my employer if you know who they are.Comment
-
-
even though its weekend, looks like it isnt doing much for you.Originally posted by pal666 View PostComment
Comment