[distcc] --no-fork

Martin Pool mbp at sourcefrog.net
Mon Feb 14 20:59:42 GMT 2005


On 14 Feb 2005, Perochon Sebastien <Sebastien.Perochon at mmarelli-se.com> wrote:

> --no-fork 
> Don't fork children for each connection, to allow attaching gdb. Don't use
> this if you don't understand it!

You can use it if you want, but it will limit the server to processing
only one job at a time.  On a single processor machine that may be fine.

> Tests have shown that using distcc under cygwin is not as powerful as under
> linux mainly because of the use of "fork".

What about the use of fork?  If the problem is that fork is slow, then
using --no-fork should not make much difference because the forking
happens only at startup and then every hundred jobs or so.

If fork is a problem, it would be more useful to replace the forks
which happen for each compilation.  Is there a more efficient way to
launch tasks in Cygwin?

--
Martin


More information about the distcc mailing list