Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

systemd just has so many reasons to kill processes, and invents new ones with new releases. Timeouts for things it thinks it should be short-lived, resource limits, service isolation and sandboxing settings, etc. They are mostly documented, but you need to know where to look. While I came to like some aspects of systemd, debugging why things die for apparently no reason after systemd was upgraded has eaten many of my workdays.


New one as of this morning is to kill STOP processes it doesn't like. I have no idea why, or how to revent it. All I did was update my 'sid' debian and here goes


> All I did was update my 'sid' debian and here goes

As it turns out it's called "unstable" for a reason


Hate to tell you, but I've been using sid for well over 20 years, and it is usually more 'stable' than most distro out there.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: