Skip to content

Only write heritrix_dmesg.log when requested - #779

Merged
ato merged 2 commits into
masterfrom
optional-dmesg-log
Oct 6, 2026
Merged

ato merged 2 commits into
masterfrom
optional-dmesg-log

Conversation

@ato

@ato ato commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

Heritrix.java always created heritrix_dmesg.log in $HERITRIX_HOME, even though only the bin/heritrix script reads it, and only when it starts Heritrix in the background. This got in the way of making $HERITRIX_HOME read-only for Docker and systemd setups.

The startup log is now written only when the heritrix.dmesg system property gives its path. bin/heritrix sets this property in background mode and keeps the file in the same place as before.

Also fix a typo in bin/heritrix ($startmessage) that stopped it removing a heritrix_dmesg.log left over from a previous start.

ato added 2 commits October 2, 2026 09:34
Heritrix.java always created heritrix_dmesg.log in $HERITRIX_HOME, even
though only the bin/heritrix script reads it, and only when it starts
Heritrix in the background. This got in the way of making
$HERITRIX_HOME read-only for Docker and systemd setups.

The startup log is now written only when the heritrix.dmesg system
property gives its path. bin/heritrix sets this property in background
mode and keeps the file in the same place as before.

Also fix a typo in bin/heritrix ($startmessage) that stopped it
removing a heritrix_dmesg.log left over from a previous start.
@ato
ato merged commit a09f385 into master Oct 6, 2026
8 checks passed
@ato
ato deleted the optional-dmesg-log branch October 6, 2026 02:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant