[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Sks-devel] and the next thing...
From: |
Robert Urban |
Subject: |
[Sks-devel] and the next thing... |
Date: |
Mon, 13 Sep 2004 20:09:43 +0200 |
Yaron Minsky wrote:
> SKS is not set-up for multi-process access to the database, and trying
> to do so will lead to corruption. sksdump does just that, and so you
> should shutdown your SKS processes before trying to run it.
>
> The proper usage is "sks dump #keys_per_file directory_to_create_dump_in"
hmm.
during testing I added a key via "gpg --send-keys ...". As I was too
lazy to delete the key, in order to test adding a key I decided to
delete it using "sks drop <key>". According to your explanation above
I must first stop "sks db" before running "sks drop", however, this
produces:
Fatal error: exception Unix.Unix_error(63, "connect", "")
When "sks db" is running, "sks drop" works.
Thus, I am again reduced to trial and error to figure out how to do
things. How about putting documentation at the top of your TODO list?
Robert Urban
- [Sks-devel] and the next thing...,
Robert Urban <=