Bug#435242: rundig: don't force "initial" database rebuild on every run
Package: htdig
Version: 1:3.2.0b6-3.1
Severity: normal
Tags: patch
while rundig in sarge would specifically test for the -i command line
option and add it to its invocation of htdig (but not htpurge)
accordingly, this test has gone away in etch, and now rundig always adds
-i to the htdig invocation.
This is quite wasteful, as -i ("initial") causes htdig to throw away the
existing database and and rebuild it from scratch, which is normally not
necessary unless content has been deleted. We index 25G of Mailman
archives, and what used to be a swift 20min nightly update run turned
into a 40h+ rebuild nightmare with several nightly updates running into
each other hogging all resources on the list server.
Hence I'd like to ask for this mandatory option to be removed, cf the
following patch:
--- /usr/bin/rundig.unpatched 2007-07-30 12:22:45.509144360 +0200
+++ /usr/bin/rundig 2007-07-30 12:23:35.983896379 +0200
@@ -54,7 +54,7 @@
TMPDIR=$DBDIR
export TMPDIR
-$BINDIR/htdig -i $opts $stats $alt
+$BINDIR/htdig $opts $stats $alt
$BINDIR/htpurge $opts $alt
case "$alt" in
-a)
Reply to: