[ apologies if you see this twice I had put a wrong address in the first one ]
Phil Pennock:
> Is it known that when you do "sks dump ", you end up with up to
> 10 stack frames per N, plus the calls into the DB layer, etc?
[...]
> I was suspecting db problems, and it's not. Looks as though some
Is it known that when you do "sks dump ", you end up with up to
10 stack frames per N, plus the calls into the DB layer, etc?
There's nothing in TODO about this, so I'm guessing not.
#26012 0x000803aabbc8 in ?? ()
#26013 0x000800f3c5d8 in ?? ()
#26014 0x000188c3 in ?? ()
#26015 0
On 2009-03-21 at 19:42 -0700, Phil Pennock wrote:
> diff --git a/sks.pod b/sks.pod
> --- a/sks.pod
> +++ b/sks.pod
[...]
> @@ -335,8 +349,9 @@ The configuration file for your SKS serv
>
> =item sksconf
>
> - logfile: log
> + initial_stat: on
> membership_reload_interval: 1
> + disable_ipv6:
This patch is relative to Yaron's repository, with *his* version of the
IPv6 patch applied. "hg log" at end of mail, to make this clearer.
Sooner or later, I'll get around to learning enough of hg to be
comfortable leaving an instance running for others to connect to, but
not yet.
Full commit mes
