There is no "large process detection". The first process that tries to fault in a new page after the system runs out of swap gets killed.
That makes sense. Me trying to connect to see what was going on would hence cause sshd to be killed ( not good ). It would seem that we could do with doing something to prevent this. We have had a few suggestions so far. 1. Using madvise, requires code changes per app 2. Using a sysctl to name processes which shouldn't be killed. 3. Changing how the choice of process to kill is made.
I don't like the idea of having to make code changes so would vote against #1. #3 I would imagine could be quite complex and error fraught so #2 seems like the best option so far.
What do others think? Go with Marc's idea?
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED]
_______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
