Bug 233565

Summary:	distcc-2.18.3-r13 on ppc uses --pidfile
Product:	Gentoo Linux	Reporter:	Mike Hammill <michael>
Component:	Current packages	Assignee:	Gentoo Cluster Team <cluster>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	2006.1
Hardware:	PPC
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Mike Hammill 2008-08-01 09:14:21 UTC

/etc/init.d/distccd contains --pidfile, however, distcc now sees this as an invalid option (should become --pid-file).

Reproducible: Always

Steps to Reproduce:
1. On ppc32, compile distcc-2.18.3-r13 (flags: gnome gtk ipv6 -avahi -selinux)
2. Attempt to start: /etc/init.d/distccd --debug start


Actual Results:  
Returns error code 102 (not specified in man distccd), but the line executed with problem was, in my case:

+ /sbin/start-stop-daemon --start --quiet --startas /usr/bin/distccd --pidfile /var/run/distccd/distccd.pid -- --pid-file /var/run/distccd/distccd.pid -N 15 --user distcc --port 3632 --log-level critical --allow 192.168.0.151 --allow 192.168.0.177 --allow 192.168.0.172 --allow 192.168.0.124 --allow 192.168.0.212 --allow 192.168.0.1 --listen 192.168.0.182


Expected Results:  
distccd starts

Note double specifying of pid file by "--pidfile" and "--pid-file".  However, distcc says, when run manually:

# /usr/bin/distccd --pidfile /var/run/distccd/distccd.pid -- --pid-file /var/run/distccd/distccd.pid -N 15 --user distcc --port 3632 --log-level critical --allow 192.168.0.151 --allow 192.168.0.177 --allow 192.168.0.172 --allow 192.168.0.124 --allow 192.168.0.212 --allow 192.168.0.1 --listen 192.168.0.182
distccd: ERROR: --pidfile: unknown option

Comment 1 Mike Hammill 2008-08-01 09:57:50 UTC

I was wrong.  The error occurs when you try to listen to an IP address with no connected machine.  (Basically, I thought the machine was on 192.168.0.182 but it was 192.168.0.181.)  I'll be glad when avahi works (or I get a brain). :-)