diff options
author | midnightveil <midnight@trainwit.ch> | 2024-05-10 15:25:12 +1000 |
---|---|---|
committer | Jade Lovelace <lix@jade.fyi> | 2024-05-16 17:11:21 -0700 |
commit | 5b7dcb3005ed38d4634f228f01852ae18b2d9cd4 (patch) | |
tree | a254515d74a24144865ae37ef468306b2e112a85 /doc/manual/rl-next | |
parent | 9322a1cbe775a32c7019a91236d9e37037b9241a (diff) |
Allow enabling core dumps from builds for nix & child processes
Fixes https://git.lix.systems/lix-project/lix/issues/268
Change-Id: I3f1b0ddf064f891cca8b53229c5c31c74cea3d9f
Diffstat (limited to 'doc/manual/rl-next')
-rw-r--r-- | doc/manual/rl-next/enable-coredumps.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/manual/rl-next/enable-coredumps.md b/doc/manual/rl-next/enable-coredumps.md new file mode 100644 index 000000000..092aa58a1 --- /dev/null +++ b/doc/manual/rl-next/enable-coredumps.md @@ -0,0 +1,13 @@ +--- +synopsis: "Add an option `enable-core-dumps` that enables core dumps from builds" +cls: 1088 +credits: midnightveil +category: Features +--- + +In the past, Lix disabled core dumps by setting the soft `RLIMIT_CORE` to 0 +unconditionally. Although this rlimit could be altered from the builder since +it is just the soft limit, this was kind of annoying to do. By passing +`--option enable-core-dumps true` to an offending build, one can now cause the +core dumps to be handled by the system in the normal way (winding up in +`coredumpctl`, say, on Linux). |