Timeline for systemd: Failed to create coredump on readonly file system
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2018 at 16:17 | vote | accept | Paul Knopf | ||
| Jul 31, 2018 at 6:22 | answer | added | filbranden | timeline score: 3 | |
| Jul 30, 2018 at 20:47 | history | edited | slm♦ | CC BY-SA 4.0 | deleted 36 characters in body |
| Jul 30, 2018 at 15:13 | history | edited | Paul Knopf | CC BY-SA 4.0 | added 179 characters in body |
| Jul 30, 2018 at 14:47 | history | edited | Paul Knopf | CC BY-SA 4.0 | added 469 characters in body |
| Jul 30, 2018 at 13:08 | comment | added | Paul Knopf | Also, this worked with systemd 234, with and without the mount --bind to /var/log before chroot. | |
| Jul 30, 2018 at 13:06 | comment | added | Paul Knopf | It has a writable overlay (tmpfs). It is completely writable. Also, if I manually mount --bind another partition to /var/log before chroot, the error still happens. | |
| Jul 30, 2018 at 13:04 | history | asked | Paul Knopf | CC BY-SA 4.0 |