22.05.2018 21:25, Carlos E. R. пишет:
On 2018-05-22 20:03, Andrei Borzenkov wrote:
22.05.2018 15:09, Carlos E. R. пишет:
On 2018-05-22 14:03, Per Jessen wrote:
Carlos E. R. wrote:
cer@Isengard:~> coredumpctl list | wc -l 452 cer@Isengard:~>
My disk would be full by now :-o
Different situation - you want to limit the space taken up by core dumps, I want plain users to be able to read their own core dumps, with a minimum of fuss.
Apparently, "coredumpctl" would give that access, but it fails to work.
I briefly tested it and it worked both on Leap 42.3 and TW for trivial test case. May be core file gets corrupted (e.g. it would exceed limit so only partial file was written).
How can I find out if that is the case?
You can try to read logs if there are anything of interest. You can try to use gdb with this file to see if it complains. You can try increase coredumpctl verbosity by setting SYSTEMD_LOG_LEVEL=debug before calling it. File size is exactly 1GiB which is rather suspicious. "readelf -a corefile" displays various sections which may give hint whether they are beyond 1GiB.