4 ms·

Playing the devil's advocate here: not every box has a writeable filesystem.

• geofft 8y ago
  I think this is the right answer - more specifically, a program may not have write access to the filesystem (e.g., with the systemd "ProtectSystem" option). Linux lets you spawn a process to handle a core dump, but I believe the process runs as if it were a child process of the crashing one, i.e., in the same namespace and with the same filesystem permissions.
• pdkl95 8y ago
  Or the only writable filesystem could be a tiny tmpfs/ramdisk. In both situations, do you even want core dumps?
  • loeg 8y ago
    https://linux.die.net/man/8/netdump https://linux.die.net/man/8/netdump https://www.freebsd.org/cgi/man.cgi?query=netdump https://www.freebsd.org/cgi/man.cgi?query=netdump
• StreamBright 8y ago
  The do not core dump.
• loeg 8y ago
  You could imagine kernel.core_pattern pointing at an NFS mount, or a psuedo-filesystem that otherwise redirected to the network (could even be a small FUSE FS, allowing for userspace handling). Of course, neither of these suggestions necessarily gives control back to systemd to then relocate or process the file. But you couldn't do that on a RO system anyway.