[distcc] distccmon loses track of a task after 60 seconds.

Fergus Henderson fergus at google.com
Fri Oct 31 15:39:54 GMT 2008

On Fri, Oct 31, 2008 at 10:26 AM, Francis Leblanc <fleblanc at matrox.com>wrote:

> Hi everyone,
> First I'd like to say that I've been very impressed about distcc since I
> started to use it, thanks to everyone that worked on this project.
> So I've found this little annoying bug in the monitor apps. Distcc is still
> working perfectly thought.
> Both distccmon-text and distccmon-gnome fail to show the process of files
> if the compilation lasts more than 60 seconds.
> In my case, using alot of templates with -O3 makes gcc slog !
> It seems that the monitor apps have a timeout of 60 seconds, in case the
> worker has been killed :
> (thank you google code search !)
> trunk/src/mon.c:74  const int dcc_phase_max_age = 60;

You can probably just change that to something larger, e.g. 1200 (to match
the default --job_lifetime specified in /etc/init.d/distcc).

> A new feature that could be added in the monitor is to add a second
> optional param,
> the max_age (or timeout) for compilation... but it seems that the 60
> seconds timeout is also hardcoded in stats.c ... :-|

The hard-coded 60 in stats.c is unrelated.

Fergus Henderson <fergus at google.com>
-------------- next part --------------
HTML attachment scrubbed and removed

More information about the distcc mailing list