On Sat, 11 Apr 2015, 03:15 -0700, David Benfell wrote:
I have just seen way too many problems with Berkeley DB in way too
many situations. It seems to be fine for small applications: postfix
uses it for really small files, for example. But anything big and it
becomes unmanageable.
Quoting John Marshall john.marsh...@riverwillow.com.au:
Perhaps the folks who have BDB problems
are the ones who mix keydump and BDB key storage?
If this is the case--and I can't rule it out--then there is the
problem of how we reliably produce keydumps for new server
administrators to
On Mon, 13 Apr 2015, 23:30 -0700, David Benfell wrote:
Quoting John Marshall john.marsh...@riverwillow.com.au:
Perhaps the folks who have BDB problems
are the ones who mix keydump and BDB key storage?
If this is the case--and I can't rule it out--then there is the
problem of how we
JM == John Marshall john.marsh...@riverwillow.com.au writes:
JM Perhaps the folks who have BDB problems
JM are the ones who mix keydump and BDB key storage?
That seems likely. ISTR having issues, too, when I tried a fast.
And there was a hickup when my dist updated from 5.1 to 5.3.
But
Hey David,
it makes me sad to see you leaving the pool, and I really hope that you'll
try to run SKS again in a few years, when the relevant problems might be
solved and bugs have been fixed. See you; don't leave us forever! :)
Best regards,
Tobias Frei
On Sat, Apr 11, 2015, 01:31 David Benfell
Hello David,
as desired I removed your server from our membership file.
I am running SKS 1.1.5+ on CentOS6 (LXC container) and CentOS7 (KVM) for
a long time w/o problems. In the past I had similar problems, but
switching clocksource to tsc solved database problems. My current
installations are
Quoting Christian Felsing c...@ip6.li:
Hello David,
as desired I removed your server from our membership file.
I am running SKS 1.1.5+ on CentOS6 (LXC container) and CentOS7 (KVM) for
a long time w/o problems. In the past I had similar problems, but
switching clocksource to tsc solved
Quoting Hendrik Grewe hendrik.gr...@tu-dortmund.de:
Also what I have read about your tries to recover the database. I
think I have read in some FAQ that one should _not_ try to recover a
(somehow) corrupted sks database. Instead one should start (from
skratch) with some actual keydump.
Among
Hi David,
On 11-04-15 12:15, David Benfell wrote:
Quoting Hendrik Grewe hendrik.gr...@tu-dortmund.de:
Also what I have read about your tries to recover the database. I
think I have read in some FAQ that one should _not_ try to recover a
(somehow) corrupted sks database. Instead one should
Hi!
As requested I have removed you from my membership file.
For informational purpouse:
I am running my sks on the tinyest VPS (parallels) from 11 it is a
special offer for students, is rate unlimited and costs 1€/year so very
very cheap (and powerless 2 gigs ram, 40 gigs discspace 1x2Ghz core).
Hello all,
There are a few folks in my membership file for whom I do not have
email addresses. This is mostly for them.
I have previously commented on the difficulty of keeping the sks
database healthy. I just discovered my sks instance had been down for
several days. I tried to recover
On 04/10/15 15:44, David Benfell wrote:
I'm giving up.
When there is an sks that uses a reliable database system, I'll be happy
to rejoin. But Berkeley DB is not sane in my environment, has never
proven scalable in any environment I've had in the past, and I'm not
messing with it any more.
Quoting Michael Sinatra michael+li...@burnttofu.net:
On 04/10/15 15:44, David Benfell wrote:
I'm giving up.
When there is an sks that uses a reliable database system, I'll be happy
to rejoin. But Berkeley DB is not sane in my environment, has never
proven scalable in any environment I've had
13 matches
Mail list logo
