[distcc] xinetd 2.3.11-1.8.0

[Jeff]

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...