the bug relates to the -a option: after successfully
building the databases they should be moved from the
work-files to their proper place. this does not happen if
you have specified an alternative db-dir in your digging
configuration due to the fact that rundig uses for the -a
parameter the default database directory.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's already a known problem, but there's no easy solution. Shell scripts
just can't easily read htdig config files, so you need to configure your
scripts to match your config files. The latest 3.2.0b4 and 3.1.6 snapshots
in http://www.htdig.org/files/snapshots/ finally document rundig, and make
a note about such configuration issues.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=383550
(sorry, i submitted too early)
the bug relates to the -a option: after successfully
building the databases they should be moved from the
work-files to their proper place. this does not happen if
you have specified an alternative db-dir in your digging
configuration due to the fact that rundig uses for the -a
parameter the default database directory.
Logged In: YES
user_id=149687
It's already a known problem, but there's no easy solution. Shell scripts
just can't easily read htdig config files, so you need to configure your
scripts to match your config files. The latest 3.2.0b4 and 3.1.6 snapshots
in http://www.htdig.org/files/snapshots/ finally document rundig, and make
a note about such configuration issues.