I'll second this question. I maintain a fork of CCache 2.4 internal to
my workplace, and I'd like to know if there's going to be some active
work on ccache.
My fork has two changes.
First, it's NFS-safe. It removes the use of non-NFS-safe fcntl() file
locking and the statistics tracking featu
I got CCache working in this scenario:
* Parallel builds, distributed across many hosts.
* CCACHE_DIR is located on NFS.
* Output files are hardlinks into the cache to save space.
Maybe this will help someone else to get it working faster than I did :)
There were two hurdles along th
This is a more elegant fix for NFS issues. It applies to ccache-2.4.
Unlike my previous patch, it doesn't create lock files, thereby avoiding
any issues with stale lock files.
- John
diff -u /home/jcoiner/ccache-2.4/ccache.c ccache-2.4_nfs_fix/ccache.c
--- /home/jcoiner/ccache-2.4/ccache.c M
Here is a second attempt at an NFS workaround.
This patch applies to ccache-2.4. The CCACHE_NFS_WORKAROUND variable
enables the workaround. This workaround requires the existence of the
"lockfile" program on the $PATH.
Here's what I think is going on, when NFS corruption occurs:
* Process X
Hi all,
Here's a patch, for ccache 2.4, which works around the NFS bug. From the
ccache man page:
"BUGS. When the cache is stored on an NFS filesystem, the filesystem
must be exported with the no_subtree_check option to make renames
between directories reliable."
I have seen corrupt object f
Ignore that patch -- this workaround does not work.
John Coiner wrote:
>
> Hi all,
>
> Here's a patch, for ccache 2.4, which works around the NFS bug. From the
> ccache man page:
>
> "BUGS. When the cache is stored on an NFS filesystem, the filesyst
