Re: [Sks-devel] Re: [PATCH] Proper case handling for words index

[Jason Harris]

On Sat, Aug 08, 2009 at 11:43:43AM +0000, Kim Minh Kaplan wrote:
> This should correct the word index.
> 
>     $ ./fix_word_index 
>     2009-08-08 13:35:41 Fixing word index
>     2009-08-08 13:38:04 Fixed 17247 words

I would suggest the output go to its own logfile, like update_subkeys:

  update_subkeys.ml:121:  set_logfile "update_subkeys";

and be verbose by default (assuming I got my extra output because I set
"debuglevel: 5" in sksconf):

  2009-08-10 11:50:40 0.090344 Opening word index
  2009-08-10 11:50:40 0.133568 Fixing word index
  2009-08-10 11:50:40 0.597982 Fix 0x65DA815FA6DE640C9B4CD96880F82E78 
00A1130001 -> 00a1130001
  ...
  2009-08-10 11:50:46 0.842120 Fix 0x0351CEB2FE16722FDE690C481C85A795 A -> a
  ...
  2009-08-10 11:58:20 0.679230 Fix 0x0A79227FF0101731FF24EFDE1CEFE3AE 
alanLovejoy -> alanlovejoy
  ...
  2009-08-10 12:06:13 0.042849 Fix 0x5768AE9CF1614392A710D2FFB4EE538C ? -> ?
  ...
  2009-08-10 12:06:13 0.608868 Fix 0x9F5C194CF96FEC513559AE05A44A3213 ??? -> ???
  2009-08-10 12:06:13 0.755021 Fixed 17458 words
  2009-08-10 12:06:13 0.755180 Closing word index

> I even believe you can run it without stopping the SKS db server but I
> am not certain, feedback on this part would be very appreciated as I am
> still investigating SKS's safety with regard to transactions.

I removed Dbenv.RECOVER from my flags a long time ago and running
./fix_word_index in parallel with "sks db" seemed to work fine.

Deadlock can still easily occur, however, since SKS doesn't yet do
full deadlock setup/handling in the BDB API, IIRC.

BTW, I would like to pull these patches directly from your repo. for
better tracking.  Thanks.

-- 
Jason Harris           |  NIC:  JH329, PGP:  This _is_ PGP-signed, isn't it?
address@hidden _|_ web:  http://keyserver.kjsl.com/~jharris/
          Got photons?   (TM), (C) 2004

pgpygAiTwujbg.pgp
Description: PGP signature