https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235125
Gordon Hartley <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gro.dsbeerf.sgub@gordonhart | |ley.com --- Comment #1 from Gordon Hartley <[email protected]> --- I think this needs the 'importance'/severity needs major escalation because I've had it kill ssh sessions where I couldn't complete backups via scp, and it's killing the ssh session I'm su'd in when trying to understand the problem. This has the potential to be one of those 'affects some people' that may transform into a case that takes out a massive amount of infrastructure that everyone depends on, and you can't remote in to solve the problem type scenarios... The result of this problem could be catastrophic in the wrong environment. My fear would be people upgrade production. Everything appears to be running smoothly for while, so safety is assumed, then whatever scenario that triggers this behaviour occurs and you can't remote in to save the system, because the system keeps killing processes involving humans trying to save the system from itself because the system veto's resource allocation for itself. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
