[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] SKS RAM usage gone haywire
From: |
Phil Pennock |
Subject: |
Re: [Sks-devel] SKS RAM usage gone haywire |
Date: |
Mon, 16 Feb 2009 17:51:24 -0800 |
-----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-----
- Re: [Sks-devel] SKS RAM usage gone haywire, (continued)
- Re: [Sks-devel] SKS RAM usage gone haywire, Phil Pennock, 2009/02/14
- Re: [Sks-devel] SKS RAM usage gone haywire, Ari Trachtenberg, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, Yaron Minsky, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, Phil Pennock, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, Ryan, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, Daniel Kahn Gillmor, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, John Marshall, 2009/02/15
- Re: [Sks-devel] SKS RAM usage gone haywire, Ryan Hunt, 2009/02/16
- Re: [Sks-devel] SKS RAM usage gone haywire, Phil Pennock, 2009/02/16
- Re: [Sks-devel] SKS RAM usage gone haywire, Ryan Hunt, 2009/02/16
- Re: [Sks-devel] SKS RAM usage gone haywire,
Phil Pennock <=
- Re: [Sks-devel] SKS RAM usage gone haywire, Ari Trachtenberg, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Azamat S. Kalimoulline, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Azamat S. Kalimoulline, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Alex Roper, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Jonathan Oxer, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, John Clizbe, 2009/02/17
- Re: [Sks-devel] SKS RAM usage gone haywire, Azamat S. Kalimoulline, 2009/02/25
- Re: [Sks-devel] SKS RAM usage gone haywire, Yaron Minsky, 2009/02/15