Bug 14540
| Summary: | ulimit -c 0 and limits -c 0 no longer disable creating core dumps | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Grigoriy Strokin <grg> |
| Component: | kern | Assignee: | Sean Eric Fagan <sef> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 3.3-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-bugs->sef sef is the author of the new coredump() in kern_sig.c (v1.63; MFC in 1.53.2.4) State Changed From-To: open->closed Version 1.53.2.6 of src/sys/kern/kern_sig.c has the fix in -stable. |
In older versions of FreeBSD one might use ulimit -c 0 to disable creation of core files. Now neither ulimit -c 0 nor limits -B -c 0 don't do what is expected: the core dumps are created, though of zero size. However, man limits says: example, if you wish to disable core dumps when starting up the usenet news system, but wish to set all other resource settings as well that apply to the 'news' account, you might use: eval `limits -U news -aBec 0` How-To-Repeat: ulimit -c 0; limits -B -c 0; cat; [press Ctrl-\] Result: the file cat.core will be created.