-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On 2009-02-16 at 17:21 -0700, Ryan Hunt wrote: > strace & corresponding recon log available @ > > http://nayr.net/sks/ > > Let me know if anymore information is needed, I since I ran this as root > my database permissions changed.. is that normal?
Whatever last created a .db file owns the file. You can chown them without problem, but you'll obviously need to do so before starting the program which runs as non-root (and running tests as root means that any permissions failures won't show up, so is more prone to heisenbugs). Eg, to create an svn repository using a bdb backend, I can use svnadmin as root then chown -R to the runtime user behind svn. Similarly for restoring an OpenLDAP setup using slapadd. I don't know sks well enough to be sure, but it looks as though your recon process is successfully dumping the keys from the remote side to diff files in /var/spool/sks/diff-$IP.txt but then timing out when talking to the db server on /var/run/sks/db_com_sock; however, your PTree lives under /var/lib/sks/PTree/. Are /var/lib/sks and /var/spool/sks the same directory? I thought that only basedir and cwd were used and the individual DBs couldn't be relocated individually. Has the cwd of the processes when they start changed? - -Phil -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkmaGBMACgkQQDBDFTkDY3/+ZACfVKS4ognyec3ynZcO6yl2MDlC RZgAn3wvRvCgaB8Ct90nXNlCKecYPOU4 =KBfE -----END PGP SIGNATURE----- _______________________________________________ Sks-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/sks-devel
