[distcc] Problems with distcc 2.18 and mandatory '--allow'

[Martin Pool]

On 29 Oct 2004, Stephen Anthony <stephena at users.sourceforge.net> wrote:
> Version:   distcc 2.18, packaged by Mandrake 10.1 Official
> Platform:   Mandrake 10.1 Official, gcc 3.4.1
> 
> There seems to be a problem with with the new mandatory --allow in 
> distcc 2.18.  I try to run the following:
> 
> distccd --daemon --user nobody --allow 192.168.0.0/24
> 
> and the result in /etc/log/syslog is:
> 
> (dcc_listen_by_addr) ERROR: bind of 0.0.0.0:3632 failed: Address already 
> in use
> dcc_exit) exit: code 102; self: 0.000000 user 0.000000 sys; children: 
> 0.000000 user 0.000000 sys
> 
> There's nothing else running on port 3632.  It's almost as if the IP 
> specified by '--allow' is conflicting with the default '0.0.0.0' used 
> by '--listen'.

It is extremely unlikely that the --allow option is causing this.  If
the kernel returns this error then the address is in use.  Maybe
something else is using that port?  What does 'netstat -ta' show?

-- 
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/distcc/attachments/20041031/d60d2236/attachment.bin