On Thu, 2018-02-15 at 20:53 -0500, Fred Smith wrote: > On Fri, Feb 16, 2018 at 12:02:28AM +0000, Patrick O'Callaghan wrote: > > On Thu, 2018-02-15 at 14:37 -0800, Joe Zeff wrote: > > > On 02/15/2018 12:20 PM, Rick Stevens wrote: > > > > "Crash save" files weren't unique to DG systems, BTW. DEC VAX/VMS did > > > > it, MAI/Basic4 did it, Tandem did it...lots of systems did it (usually > > > > using different nomenclatures). Heck, vi/vim does it in a way (via ye > > > > ol' ".filename.swp" backup file). > > > > > > If memory serves, Unix used "core" for that, and it was an actual core dump. > > > > That's correct. It's also correct for Linux, except that by default the > > core dump is normally turned off and you have to enable it (see 'man > > core'). > > > > poc > > I always use "ulimit -c unlimited" to enable coredumps. is there a > more preferred way? AFAIK that just affects the size limit, however it appears that it's already unlimited by default. Contrary to what I said earlier, core dumps are not disabled by default. I misread the man page. However the whole story depends on several other factors, including sysctl(5) settings and systemd- coredump(5) (surprise!), for which the documentation is causing me to lose the will to live. Normally this is configured so the abrtd daemon watches for them and decides what to do based on yet more settings in abrt.conf(5). TL;DR: yes, there are still core dumps. They can usually be found under /var/spool/abrt (root access only). poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
