In message <9509290728.AA05326@ncc.ripe.net>, Willi Huber writes:
Dear all,
The last days I did some further research with Benoit Grange and Willi Huber (they both run SUN OS, so we could use each others binaries) on the recent indexing problems. This morning I found out that the problems disappear when you don't use the '-p' prime option in netdbm. This option adds dummy objects to the database to make the lookups faster.
So for the temporary solution:
Do *NOT* use the '-p' option in netdbm !!!
I am not sure yet if there is a bug in the code or that certain 'dbm' versions cause the problems. I will investigate further ...
Kind regards,
David Kessens RIPE NCC Database software maintainer --------
Without '-p' option the script has completed without 'file system full'. So we have again some time to go.
Willi Huber SWITCH
We get much smaller files. At David Kessen's request I tried this with -p to see if it made any difference. It doesn't. It appears the differnce is simply BSD DB vs DBM. I normally use -cfMV with the code I run. I cleaned the directory and the added "p" yielding -pcfMV. The results were: [curtis@figaro.ans.net 5] ls -ltr test total 51856 -rw-r----- 1 curtis staff 22044885 Sep 29 00:27 ripe.db.save -rw-r----- 1 curtis staff 16384 Sep 29 18:08 ripe.db.save.db -rw-r----- 1 curtis staff 4448256 Sep 29 18:08 ripe.db.save.cl.db [curtis@figaro.ans.net 6] du -s test 51858 test We are running modified code (some of the flags are not in the RIPE distributed code, but all our code recently went to David). Anyone can get the same effect relinkink BSD DB and looking for the few places in the .pl files where .pag or .dir is found. Curtis