[distcc] xinetd 2.3.11-1.8.0

Martin Pool mbp at samba.org
Tue May 20 01:50:57 GMT 2003


On 19 May 2003, Jeff <rustysawdust at yahoo.com> wrote:
> Last week Red Hat released an updated xinetd, 2.3.11-1.8.0, and I've 
> noticed that the machines on which I've done this upgrade no longer 
> accept distcc connections! The machines which didn't get the upgrade 
> still seem to work OK.
> 
> When I turn on verbose output, I see the following errors repeated over 
> & over. Is anyone else having this problem?
> 
> distcc[4420] (dcc_lock_host) 
> /tmp/distcc_000075b1/lock_cpu_tcp_cow_3632_0 is busy
> distcc[4420] (dcc_lock_host) got cpu lock on cow slot 1
> distcc[4420] (dcc_lock_host) 
> /tmp/distcc_000075b1/lock_xmit_tcp_cow_3632_0 is busy
> distcc[4420] (dcc_unlock) release lock
> distcc[4420] (dcc_lock_host) got cpu lock on cow slot 2
> distcc[4420] (dcc_lock_host) 
> /tmp/distcc_000075b1/lock_xmit_tcp_cow_3632_0 is busy
> distcc[4420] (dcc_unlock) release lock
> distcc[4420] (dcc_lock_host) got cpu lock on cow slot 3
> distcc[4420] (dcc_lock_host) 
> /tmp/distcc_000075b1/lock_xmit_tcp_cow_3632_0 is busy
> distcc[4420] (dcc_unlock) release lock
> distcc[4420] (dcc_lock_pause) nothing available, sleeping...

These probably just mean that the client is blocking trying to connect
to the server.  So it tells you that 'cow' is not refusing
connections, but it's not making much progress either.

Can you have a look in the log on the server for messages from either
xinetd or distccd?

-- 
Martin 



More information about the distcc mailing list