Hi John-- thanks for the followup!
On 07/27/2012 12:59 AM, John Clizbe wrote:
> echo "KDB --"
> cd KDB
> sudo db53_recover -ev
> sudo db53_checkpoint -1
> sudo db53_archive -dv
> sudo db53_recover -ev
> cd ..
>
> echo "PTree --"
> cd PTree
> sudo db53_recover -ev
> sudo db53_checkpoint -1
> sudo db53_archive -dv
> sudo db53_recover -ev
Should these db commands really be run by the superuser (sudo), or
should they be run by the owner of the directory and files?
> You might have gotten away with just the db_recover script above and restarted
> the sks processes. You might have locked up again, but that probably had more
> to do with a massive recon set than anything else.
having just completed in a large set (a full month's worth of data) from
zimmermann's peers, i can attest that a massive recon with marco's sks
1.1.3 from squeeze-backports actually works fine, and doesn't cause the
server to lock up (though it does put a strain on the kernel's IO
subsystem).
Regards,
--dkg
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
