you can spin up a second instance on the same host, perhaps bound to and Have your public instance also peer
with the localhost-only instance, and the locallhost-only instance peer
only with your public instance. Then you can start and stop the
localhost-only instance to dump it.

On Sun, Feb 4, 2018 at 4:26 PM, Hendrik Visage <>

> Good day,
>  As I can’t dump the SKS database while running, and the file snapshot
> setup not quite feasible for my setup(s) yet, I was wondering about a
> gossiping only server (and only gossiping to a limited set servers close
> peers) that isn’t connected/advertised to the SKS pool.
>  This would then be a server I could easily take offline and dump keys
> every so often, not impacting the pool availability etc.
> Which settings should I use to achieve the above, as it seems the moment I
> start the server, it starts to broadcast it’s availability to be included
> in the pool?
> ---
> Hendrik Visage
> HeViS.Co Systems Pty Ltd
> T/A Envisage Systems / Envisage Cloud Solutions
> +27-84-612-5345 <+27%2084%20612%205345> or +27-21-945-1192
> <+27%2021%20945%201192>
> _______________________________________________
> Sks-devel mailing list

GDB has a 'break' feature; why doesn't it have 'fix' too?
Sks-devel mailing list

Reply via email to