On Sat, 2003-09-20 at 19:37, Martin Pool wrote: > Why do you make the directories setuid? Does that even do anything?
This was fixed with a new patch.
> > 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.
>
> Are you *sure* the lock file was created by the distcc process?
> (i.e., can you delete the lockfile, run distcc, and then show that it
> has been created?) That seems extremely unlikely. Perhaps they were
> created by some other process?
The problem is that Portage is invoking '`which gcc` -dumpversion'
through distcc, for some reason or another, and distcc is creating a
lock file owned by root. So its a "Lisa jumped the gun, even though she
was so sure" problem and not a distcc problem. ("oops")
--
Regards,
-Lisa
<Vix ulla tam iniqua pax, quin bello vel aequissimo sit potior>
signature.asc
Description: This is a digitally signed message part
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
