>     Maybe if I call the sysctl "vm.crashmenow".  No, that will just make more
>     people actually try it.  It might be doable as a compile-time option,
>     since you wouldn't be able to run anything approaching standard on
>     such a system anyway.  I don't see much use for it myself.  As I said
>     before, there are easier ways to manage memory that are not quite as
>     arbitrary as simply refusing a potential overcommit.

Perhaps it could be an additional flag to mmap, in this way
people wishing to run an overcommited system could do so
but those writing programs which must not overcommit for
certain memory allocations could ensure they did not do so.

Regards,

Niall