Xavier de Gaye <[email protected]> added the comment:
Oh it seems your Fedora 27 also uses systemd and uses the same configuration as
archlinux, see https://wiki.archlinux.org/index.php/Core_dump. In that case
according to this wiki your core dumps go to /var/lib/systemd/coredump and this
may explain the different behaviors between your system and mine.
My setup (updating the file /etc/sysctl.d/50-coredump.conf) was the documented
archlinux practice 4 years ago when systemd used to store the coredumps in log
files (very annoying). This setup is still working although it is not
documented in this wiki (maybe somewhere else).
FWIW I have kept the notes made when configuring archlinux at that time, they
are:
disable core dumps managed by systemd-coredumpctl(1) - see also man pages for
sysctl.d and sysctl
/etc/sysctl.d/50-coredump.conf # same file name as in
/usr/lib/sysctl.d/
kernel.core_pattern=core-%e.%s
echo "core-%e.%s" > /proc/sys/kernel/core_pattern # or reboot
# per user
ulimit -c unlimited
----------
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue32252>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
