You are not logged in.
Some of the packages I build generate lots of coredumps during build.
The coredumps don't affect build success/failure, but do slow down things a lot.
I often execute ulimit c 0 before building so no coredump logs are created but do tend to forget it.
Disabling coredump logging permanently feels a bit risky to me as those logs could have important information for troubleshooting hardware problems when they occur.
What would be a clean methoid to disable coredump logging for makepkg / clean chroot builds but not for other processes ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
The local wiki entry for coredump has a sysctl solution. I don't know much about your relationship with systemd, but it looks like one can turn coredumps off and on on the fly. That wouldn't cover all edge cases, but might be good enough.
Online
Thanks for the reply, I'll consider it.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline