From: Jennifer Z. <we...@ca...> - 2004-08-31 17:36:06
|
Sue enough, the conf file (second one) was corrupted. Thanks! Jen On Aug 30, 2004, at 11:47 PM, Jim wrote: > On Mon, 30 Aug 2004, Jennifer Zelazny wrote: > >> Hello. I have a need to have 2 different conf files and 2 separate >> databases with my ht://Dig 3.1.6 install to keep my public and >> private sections of my web site separate. In my first conf file, I >> have defined the database_dir: as /Volumes/www/htdig/db/public. >> >> I then run rundig and define the public conf file: >> /Volumes/www/htdig/bin/rundig -c >> /Volumes/www/htdig/conf/public_htdig.conf. This works as expected, >> all the db files go into the public folder defined in my public.conf >> file. >> >> When I go to run rundig to build the databases for the private side >> of the web site, with the database_dir: >> /Volumes/www/htdig/db/private, all the db files go into >> /Volumes/www/htdig/db/ and not /Volumes/www/htdig/db/private like >> specified in my conf file. >> >> Any thoughts why this would work with the first and not the second? > > I would start by removing the config file you are using for the > private part of the site and replacing it with the public_htdig.conf > file that appears to be working. Then carefully edit the new copy, > making just those changes necessary for the private site. I suggest > this because it sounds like your config file for the private site > might have somehow been corrupted (e.g. a non-printing character or > syntax error that is causing > causing problems with the parsing of the file). > > Also double and triple check your command line to ensure that you are > passing the correct config file. > > Are you using the same copy of rundig for both cases? If not, carefully > check the scripts to make sure that they are doing what you expect. > > Jim |