| Summary: | maxproc needs a default value | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Stefan Rink <stefanrink> |
| Component: | conf | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | New --- | ||
| Severity: | Affects Many People | CC: | emaste, sigsys |
| Priority: | --- | Keywords: | crash |
| Version: | 12.0-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
It's hard to pick a sensible default though. OpenBSD has default (per architecture) rlimits, which I think is a good idea, but they often have to be changed. There's kern.maxprocperuid which can default to something calculated based on hardware resources. It's set a bit lower than maxproc as it is, but not enough to protect the system in most cases it seems. A process count limit alone only protects you against accidental fork bombs. And then again, it probably only protects other users from it, it's pretty hard to recover your session when you can't spawn more processes. I guess that's the reason it hasn't been done already, it's not a good protection by itself and setting a whole bunch of resource limits is too difficult (and required to set very low per-process limits to be effective before rctl). |
Creating a shell file with something like $0&$0& will kill any FreeBSD machine with the default configuration. (Also kills the host when you try this in a jail) In bash; :() { :|: & };: There should be at least some default value set for maxproc in login.conf, unlimited is asking for trouble. :-) Be careful with this, it takes down your machine hard and only recovery is power cycle or hard reset.