Jaromir Dolecek <jdolecek@netbsd.org> writes:
> > You've made an unconfigurable change that impacts what has been acceptable
> > behavior FOR DECADES. Either revert it, or sysctl it with a default of
> > zero.
> 
> I think that this makes most sense. It can trivially be switched on
> for systems where this would be useful (or when actual fork-bomb lands),
> but wouldn't do anything to people who don't explicitly turn it on. 
> Would everyone be happy with this? Perry, Thor, Michael, others?

I would accept either a sysctl or a compile time option, default
off. If it isn't on by default, I'm going to be unimpacted so I'll be
happy.

-- 
Perry E. Metzger		perry@piermont.com