During coredump generation I could find a temporary uncompressed file getting generated from the corefile and written to the harddisk, later this file is getting compressed (if compression was enabled) and then the file coredump file is stored and this temporary file is removed.
I have a process whose memory consumption is typically around 5GB, it generates around 13GB of uncompressed coredump ( coredump_filter = 0x33). Later this file is compressed to 20MB and the uncompressed file is removed. I have set the ProcessSizeMax=16GB ExternalSizeMax= 16GB But sometimes my disk doesn't have sufficient space to store this temporary file, hence systemd-coredump aborts the coredump processing. Is it possible to skip this temporary file generation and generate the compressed file directly from the Corefile passed through STDIN? Is there any impact on doing so? I tried modifying the coredump.c and was able to get this compressed file directly from the core file. But I am not sure on whether it will fail on some scenarios or I am missing some important data. Also please let me know if my understanding of systemd coredump behaviour is wrong.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
