On October 31, 2004 01:20 am, Martin Pool wrote: > On 29 Oct 2004, Stephen Anthony <[EMAIL PROTECTED]> 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?
You're right, it was a problem with the distro overwriting my settings. I was using distcc in daemon mode, and turned it off in xinetd. But when I recently upgraded to Mandrake 10.1, it made distcc be launched from xinetd again. Hence the 'address already in use' when I tried to launch in daemon mode. So this is a distro bug. Thanks for the quick response. Steve __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/distcc