[distcc] Minor bug in distcc using --listen: Address already in use

[Flynn Marquardt]

Hello,

I'm running distcc with the --listen option:

/usr/bin/distccd --log-file=/var/log/distccd.log --no-detach --user
distccd --listen 192.168.33.1 --allow 192.168.33.0/24

and get the following log messages:

distccd[3547] (dcc_listen_by_addr) ERROR: bind of 192.168.33.1:3632
failed: Address already in use
distccd[3547] (dcc_exit) exit: code 102; self: 0.000000 user 0.010000
sys; children: 0.000000 user 0.000000 sys
distccd[3548] (dcc_setup_daemon_path) daemon's PATH is
/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin
distccd[3548] (dcc_should_be_inetd) stdin is a tty; assuming --daemon
mode
distccd[3548] (dcc_listen_by_addr) ERROR: bind of 192.168.33.1:3632
failed: Address already in use
distccd[3548] (dcc_exit) exit: code 102; self: 0.000000 user 0.010000
sys; children: 0.000000 user 0.000000 sys
distccd[3549] (dcc_setup_daemon_path) daemon's PATH is
/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin
distccd[3549] (dcc_should_be_inetd) stdin is a tty; assuming --daemon
mode
distccd[3549] (dcc_listen_by_addr) ERROR: bind of 192.168.33.1:3632
failed: Address already in use
distccd[3549] (dcc_exit) exit: code 102; self: 0.000000 user 0.010000
sys; children: 0.000000 user 0.000000 sys

It seems that every forked process tries to bind to the already used
socket, this does happen without the --listen option.

I'm using the current version of distcc 

nilf:~# distcc --version
distcc 2.11.2 i386-pc-linux-gnu (protocols 1 and 2) (default port 3632)
  built Nov  7 2003 20:00:09

Otherwise all is running fine.

Will there be a support for compiling java sources?

Flynn