> > At first sight memory footprint of sks recon is drastically reduced.
>
> ... but after a few hours suddenly it grew again.
> http://bakacsin.ki.iif.hu/~kissg/tmp/memory-day.png
> May be hunt for misbehaving peers.
Flow analysis shows almost no traffic on port 11370
yesterday between 21:20 an
> > > for my server, i have
> > >
> > > # max cache DB
> > > cache: 80
> >
> > I have no such settings.
> > sksconf is unchanged since Dec 17 2013.
> >
> > Now I add this entry. Then I listen and wait. :-)
>
> At first sight memory footprint of sks recon is drastically reduced.
... but after
> > for my server, i have
> >
> > # max cache DB
> > cache: 80
>
> I have no such settings.
> sksconf is unchanged since Dec 17 2013.
>
> Now I add this entry. Then I listen and wait. :-)
At first sight memory footprint of sks recon is drastically reduced.
Thanks again.
Gabor
--
"Wenn ist d
Dear Robert,
> Did you check the cache value in /etc/sks/sksconf.
>
> for my server, i have
>
> # max cache DB
> cache: 80
I have no such settings.
sksconf is unchanged since Dec 17 2013.
Now I add this entry. Then I listen and wait. :-)
Thanks.
Gabor
--
A mug of beer, please. Shaken, not
hi ,
Did you check the cache value in /etc/sks/sksconf.
for my server, i have
# max cache DB
cache: 80
regards
robert
===
Le 12/03/2015 16:19, Gabor Kiss a écrit :
>> Last Friday I reorganized disk partitions used by SKS.
>> At first sight it was all right but now I found, that
>> recon proce
Gabor Kiss writes:
> Any idea?
May be hunt for misbehaving peers.
--
Kim Minh
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel
