On Mon, 2016-12-05 at 11:50 -0600, Michael Catanzaro wrote: > On Mon, 2016-12-05 at 17:03 +0000, Zbigniew Jędrzejewski-Szmek wrote: > > That's misleading. Current behaviour of systemd-coredump is to store > > the metadata in the journal, and the coredump on disk. Storing it in > > the journal was rather inefficient, and we backed away from this. I > > think saying "Core dumps will be processed by systemd-coredump and > > information about core dumps will be stored in the journal" or > > something along those lines would be better. > > OK, I revised the change page to reflect this. > > > > rather than created in the crashing process's current working > > > directory by ABRT > > > > Doesn't abrt store the coredumps in /var/tmp? > > If you set ulimit it creates the core dumps in cwd. At least it did in > F23; it's probably broken in F24 due to SELinux or systemd or something > or other, but creating core dumps in cwd is definitely the previous and > intended Fedora behavior. So far as I've seen, it always stores them in /var/spool/abrt . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
