Thanks for all the replies. Is it best to just do a few hours at a time, then ./index -E / ./index -D then restart again ./index -N 50 -R 50? In other words, just doing a bit at a time as opposed to doing the entire run in one shot?
I was also asking if anyone knew about the behaviour of making changes in the conf file. I got a lot of good answers, but nothing on this one :). When I make changes to the conf file, are they taken into account right away or only after everything is done or I use ./index -E to quit then restart? It would be *great* if it were live because then we could fine tune everything as it's working and never really have to stop anything unless you had a reason to. Mike >Before I run the indexer I look at the current stats: > >../index -S > >Now I know what I'm dealing with before I start. Then I run the >indexer: > >../index -N 80 -R 64 > >When I want to stop the process I do (from another prompt of course): > >../index -E > >Then I build the deltas: > >../index -D > >I then do what ever and again check the stats: > >../index -S > >I then compare my figures. Next I restart the process: > >../index -N 80 -R 64 > >and things work as expected without restarting from the begining. > >One time it did start all over. In fact indexer was in a loop. The >reason was that I had the "Period" in aspseek.conf incorrectly used. >I mixed "M"inutes with "m"onth which instead of reindexing every >month like I thought, I set it to reindex every minute which caused >everything to loop. Other than that the indexing worked OK. Sure I >have other problems as does most everyone else does I'm sure, but >not the problem you are having. > >Regards, >Karen
