[distcc] Limiting cpp0, randomizing hosts, more verbose localhost lockfile names

[Donohue, Michael]

I've found the FAQ has a couple questions about NFS.   Namely, "Files
written to NFS filesystems are corrupt" and "distccmon doesn't work on
NFS"

These seem more like warnings than prohibitions, and indeed, we haven't
had any problems with object files full of zeros, and distccmon has been
modified here so that it doesn't do orphan detection.  Instead the
status files get removed after a minute or so.

I'll try some tests tonight when our developers aren't all using the
machines, to compare a network mounted lock directory to a local one,
but I have no evidence that getting a lock is causing any performance
problems, so I will be surprised if there is a difference.

Michael

-----Original Message-----
From: Daniel Kegel [mailto:dank at kegel.com] 

standard distcc practice is to *not* use network shared directories
for the lockfiles.   Can you test putting the lockfiles on a local
disk and see if that improves performance over your current results?
-----End Original Message-----