[distcc] Error "Transport endpoint is not connected"
Jean Delvare
khali at linux-fr.org
Thu Feb 10 20:37:40 GMT 2005
Hi Martin & all,
> > Remember that you need to run distccd on both machines, not just the
> > compile-server. Your local distcc client will connect to the local
> > distccd daemon, which itself will connect to the remote distccd. The
> > local distcc client cannot connect to the remote server directly. At
> > least this is how I understood it.
>
> No, that is incorrect. The client program sends directly to the
> remote server. You do not need a server running on a machine that
> only acts as a client.
Oops, sorry for spreading misinformation then :( I must have misread the
documentation somehow, or just have a very poor memory.
Am I still correct in thinking that, in order to use localhost for the
compilation, one has to run distccd on it? Or is it wrong too?
I start wondering how distccmon-* get its data if not querying the local
distccd. Simply polling files in ~/.distcc?
Thanks,
--
Jean Delvare
More information about the distcc
mailing list