Distributors ponder a systemd change
Distributors ponder a systemd change
Posted Jun 8, 2016 11:56 UTC (Wed) by ras (subscriber, #33059)In reply to: Distributors ponder a systemd change by matthias
Parent article: Distributors ponder a systemd change
I remember I have had a process going infinite on logout, but can't actually recall when - it was a long time ago. Infinite loops after getting a sighup must be easy to track down.
What I can recall happening recently is a kernel driver misbehaving. I go through the rmmod, modprobe dance. But instead of fixing it the processes using the driver hangs on some unbreakable kernel lock, and the eventual kill -9 is a complete waste of time. The only way out is a reboot of a production machine. I gather race conditions during module removal are unavoidable, and regardless there always seems to be more of them. If the systemd or gnome guys have a fix for this, no matter how bad, I promise to call it a thing of beauty.
But using this sledge hammer to cure a simple infinite loop bug, and break backward compatibility - sorry, no.
Posted Jun 8, 2016 13:51 UTC (Wed)
by bronson (subscriber, #4806)
[Link] (1 responses)
Posted Jun 8, 2016 22:03 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link]
Posted Jun 8, 2016 14:51 UTC (Wed)
by diegor (subscriber, #1967)
[Link]
Usually process for which kernel is serving a system call, can not be interrupted, until kernel have finished.
Distributors ponder a systemd change
Distributors ponder a systemd change
Distributors ponder a systemd change