Hi,
Analysing something in the distccd logfile yesterday I noticed the
following improvements may speed up problem determination ;)
+ Timestamps, when using --log-file there are no timestamps.
+ A lot is logged that I'd rather omit by default as the more lines a
compile-job takes, the less you can see and the more dificult it is to
have an overview
And since it is always better to have an example, here is mine ;))
distccd[3845] (dcc_check_client) connection from 10.15.0.11:33210
distccd[3845] compile from conftest.c to conftest.o
distccd[3845] (dcc_r_file_timed) 86312 bytes received in 0.022197s, rate
3797kB/s
distccd[3845] (dcc_collect_child) cc times: user 0.090000s, system 0.010000s,
621 minflt, 836 majflt
distccd[3845] i386-redhat-linux-gcc-2.96 on localhost completed ok
distccd[3845] job complete
I'd make a distinction between 3 phases
1. Connection
2. Compile start
3. Compile end
So the default log may say something like:
Jul 31 04:17:19 distccd[3845] Connection: lisse.local.blah:33210
Jul 31 04:17:20 distccd[3845] Input: conftest.c (86312 bytes in 0.022197s at
3797kB/s)
Jul 31 04:17:23 distccd[3845] Output: conftest.o (using
i386-redhat-linux-gcc-2.96) OK
Of course the details may differ but I'd output a lot less by default (so
without explicitly adding debugging flags). And of course if things fail
something in the same spirit.
Thanks ;)
-- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
__
distcc mailing list http://distcc.samba.org/
To unsubscribe or change options:
http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
