Thanks for your good report. The log shows that shortly after the server forks to run the compiler, the child just exits without doing anything. It is successfully logging one message, so that we know its log messages are not being lost. It is not crashing, or otherwise the parent would log that fact.
I don't know what would cause that problem. Is there anything unusual about the server machine's configuration? Could you try running it under strace? strace -o /tmp/distccd.trace -f distccd --wizard -- Martin __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/distcc
