Hi, When I do a search in susehelp, some sections do not work: Administration Guide Htdig error: Unable to read configuration file User Guide Htdig error: Unable to read configuration file Bash Reference Htdig error: Unable to read configuration file To which "configuration file" is it refering to? -- Cheers, Carlos Robinson
* Carlos E. R.;
Hi, Htdig error:
Unable to read configuration file
User Guide Htdig error: To which "configuration file" is it refering to?
Which SuSE version ? -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
The 03.08.06 at 14:44, Togan Muftuoglu wrote:
To which "configuration file" is it refering to?
Which SuSE version ?
8.2, updated from 8.1. I think there were stale indexes from 8.1 that were not rebuilt. It needed an "/usr/bin/susehelpindex --force" to force them to be made. -- Cheers, Carlos Robinson
On Wednesday 06 August 2003 07:04 am, Carlos E. R. wrote:
Hi,
When I do a search in susehelp, some sections do not work:
Administration Guide Htdig error:
Unable to read configuration file
User Guide Htdig error:
Unable to read configuration file
Bash Reference Htdig error:
Unable to read configuration file
To which "configuration file" is it refering to?
-- Cheers, Carlos Robinson
Hi Carlos, I think it's referring to the htdig.conf file in /srv/www/htdig/conf but I'm not positive. You might want to try rebuilding the search index prior to looking into this further. -- Freedom is just chaos with better lighting. ---------------------------------------------------------------- SuSE 8.2 - KDE 3.1.3 Darl McBride is a fscking diskhead
The 03.08.06 at 08:03, columbo wrote:
I think it's referring to the htdig.conf file in /srv/www/htdig/conf but I'm not positive. You might want to try rebuilding the search index prior to looking into this further.
There is a bunch of files in "/srv/www/htdig/conf", including "htdig.conf", "bash.conf", "suselinux-adminguide.en.conf" and "suselinux-userguide.en.conf". Creating the index appears to work - I have tried before: nimrodel:~ # SuSEconfig --module susehelp Starting SuSEconfig, the SuSE Configuration Tool... Running module susehelp only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.susehelp... Creating susehelp index. Finished. And: nimrodel:~ # /usr/bin/susehelpindex Creating index files... No indexable documents. But the errors remain. Mmm, I have an idea: nimrodel:~ # /usr/bin/susehelpindex --force --verbose Creating index files... Execute: /usr/share/susehelp/genhtdig.pl /usr/share/susehelp/meta/SuSE/suselinux-adminguide.en.desktop ... Created index for 25 documents. Ok, it worked! They show on the search page. -- Cheers, Carlos Robinson
On Wednesday 06 August 2003 07:21, Carlos E. R. wrote:
Created index for 25 documents.
Ok, it worked! They show on the search page.
You can set this to run every time you run SuSEconfig in the YaST sysconfig editor (Applications-SuSEhelp-DOC_AUTOINDEX). -- Scott Jones (scott at exti dot net)
The 03.08.06 at 15:16, Scott Jones wrote:
You can set this to run every time you run SuSEconfig in the YaST sysconfig editor (Applications-SuSEhelp-DOC_AUTOINDEX).
It was set. I had to manually run the command " /usr/bin/susehelpindex --force" - the "force" made it work. This error happened, I think, because I updated from 8.1 to 8.2, and there were stale indexes left over from 8.1 -- Cheers, Carlos Robinson
Scott Jones
You can set this to run every time you run SuSEconfig in the YaST sysconfig editor (Applications-SuSEhelp-DOC_AUTOINDEX).
Be sure you have the update for susehelp, otherwise the automatic creation of the index won't work because of wrong paths in the scripts. Philipp -- Philipp Thomas work: pthomas@suse.de private: philipp.thomas@t-link.de
participants (5)
-
Carlos E. R. -
columbo -
Philipp Thomas -
Scott Jones -
Togan Muftuoglu