Hi,
I have some (Debian/Slackware) VPS to spare and wonder about the
resources needed to run SKS in the pool of keyservers. I'd build the
database offsite and just transfer it, bandwidth is not an issue. RAM
and CPU usage are, however.
Could someone running SKS in a VPS please comment on this?
On Wed, 20 Apr 2011 15:54:38 +0200
markus reichelt m...@mareichelt.com wrote:
Hi,
I have some (Debian/Slackware) VPS to spare and wonder about the
resources needed to run SKS in the pool of keyservers. I'd build the
database offsite and just transfer it, bandwidth is not an issue. RAM
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sebastian Urbach wrote, On 04/20/2011 04:10 PM:
On Wed, 20 Apr 2011 15:54:38 +0200
markus reichelt m...@mareichelt.com wrote:
Hi,
I have some (Debian/Slackware) VPS to spare and wonder about the
resources needed to run SKS in the pool of
I have some (Debian/Slackware) VPS to spare and wonder about the
resources needed to run SKS in the pool of keyservers. I'd build the
database offsite and just transfer it, bandwidth is not an issue. RAM
and CPU usage are, however.
Partial answer:
Two processes are running.
$ ps uww 14230
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Are there any recommendations for the number of peers each keyserver
should have in the membership file?
I'm hesitant to add each and every peering offer, but also want to
ensure my keyserver stays current even if one, or a few, peers are down
for
Hi all,
I'm mystified as to how I even got into this:
PANIC: fatal region error detected; run recovery
I see about running db_recover:
debian-sks@atlanta:~/DB$ db4.8_recover -v
Finding last valid log LSN: file: 22 offset 120
Recovery starting from [21][657]
Recovery complete at Wed Apr 20
Are there any recommendations for the number of peers each keyserver
should have in the membership file?
Not yet. :-)
In theory an optimal value could be computed but there are
too many parameters (e.g. network delay and bandwidth,
probability of hardware errors, average length of outages,
cpu
On Apr 21, 2011, at 12:38 AM, Gabor Kiss wrote:
Are there any recommendations for the number of peers each keyserver
should have in the membership file?
Not yet. :-)
In theory an optimal value could be computed but there are
too many parameters (e.g. network delay and bandwidth,
