Re: [APC-DEV] Spurious writes to /tmp

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Brian,

> The /tmp/.apc.XXXXXX files are created because you're using file locking
> (the default):
> 
> apc_fcntl.c:
>     40         char lock_path[] = "/tmp/.apc.XXXXXX";

Aha.

> If it's of use to you we could probably make this more path more
> configurable, but as a solution to get you up and running fixing /tmp
> permissions is one way.  You can also try out the IPC Semaphore,
> pthread, or spin locks out as well (pthread and spin locks being the
> fastest choices).

I think the best way forward is to move straight to the new locking
mechanisms. More than happy to beta test them a bit.

I've now rebuilt with --enable-apc-spinlocks and the SELinux warnings
have gone away. Everything seems to be working still, so I'll go with
this solution!

Thanks for your help,

- --
Jay L. T. Cornwall, http://www.esuna.co.uk/~jay/
PhD Student
Imperial College London
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGPiK3oHnC75cy2zgRAkbSAKCRUYj1tW2XxevXlCiifiDHdqqjgQCfSdhf
5rp0dPTWJde7UaJm3Dpj3BA=
=Jz7N
-----END PGP SIGNATURE-----