[distcc] A bug in distcc?

[Lisa Seelye]

I've seen some very weird behavior while integrating distcc with
Portage.

We've made a patch to Portage[1] to extend the way that Portage works
with distcc.  In a nutshell, the patch provides DISTCC_DIR envvar and
also creates the directory for use by distcc for state and lock files
and chown's portage:portage them.

The bug comes into play when Distcc tries to write the lock files:

distcc[8182] (dcc_open_lockfile) ERROR: failed to creat
/var/tmp/portage/.distcc/lock/cpu_localhost_0: Permission denied
distcc[8182] (dcc_lock_one) ERROR: failed to lock

But, the lock file _was_ created; and the monitors work.

I emerged distcc as a test and the log is online at my website[2].

1: Gentoo Bug 29171 http://bugs.gentoo.org/show_bug.cgi?id=29171
2: http://dev.gentoo.org/~lisa/distcc/log.distcc
-- 
Regards,
-Lisa
<Vix ulla tam iniqua pax, quin bello vel aequissimo sit potior>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/distcc/attachments/20030920/b1964853/attachment.bin