| Summary: | rc.conf(5) manpage mentions defunct savecore_enable option | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Nathan Ahlstrom <nrahlstr> | ||||
| Component: | conf | Assignee: | Sheldon Hearn <sheldonh> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | 3.3-STABLE | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Responsible Changed From-To: freebsd-bugs->sheldonh I'll take this one. State Changed From-To: open->closed I didn't use the submitted diff, because the dumpdev description was inadequate in the absence of the savecore_enable option. See the diff (I've committed a similar fix to HEAD and RELENG_3). Thanks for reporting this. :-) |
The rc.conf.5 manpage mentions the savecore_enable option. This has been replaced by simply defining a dumpdev. Fix: Here is a patch to rc.conf.5: How-To-Repeat: Attempt to enable savecore via this option. Read /etc/rc: # enable dumpdev so that savecore can see it # /var/crash should be a directory or a symbolic link # to the crash directory if core dumps are to be saved. if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then dumpon ${dumpdev} echo -n checking for core dump... savecore /var/crash fi