Author: lisa

Truthfully that would be kind of nice. I could really trim down the distcc documentation and the ebuild to remove the stuff that is only present to deal with pre-bootstrap.

With Bug 80219 we’re going to be adding SLP support to distcc. It will be a boon for those people with large clusters of volunteers.

Right now it seems to work. The daemon starts (./distccd -p 3666 –listen 192.168.0.254 -a 192.168.0.0/24 -P /home/lisa/projects/distcc/distcc-2.18.3/src/distccd.pid –verbose –log-level=debug –log-file=./log.log –daemon) and the tool works (./distccenv —> DISTCC_HOSTS=”lithium:3666 “).

I wonder if the portage guys could do a test to see if slpd is running and use that to set DISTCC_HOSTS with the distccenv program: export `distccenv`. I haven’t done any compilation tests just yet.

---

On Distcc and bootstrap:

One of the major problems with using distcc during installation from stage 1 is that the user must manually add the distcc user before issuing the emerge distcc command. When the user later (after stage 2) installs distcc the shadow package is available for useradd.

I’d love to just make it so the user has to re-emerge distcc after bootstrap. I think I may have found a MAJOR brain fart: Currently the distcc use is required during emerge to change the permissions of /var/run/distccd to that user so the init script can put the pid file there, owned by distcc:daemon. Inside the init script the directory is chmodded again for the distcc user. Why add do it in the ebuild when it can be done in the init script? *duh* I’ll test that with the SLP stuff.

I finally inherited my fianc

Well I’m back in New York, as of the 12th. I suppose a short update is in order…

Everything in Trinidad went well. Thank you to everyone for your help, you know who you are.

Anne and I are scheduled to fly back to England on the 24th of October. This will go ahead if I have my passport! A critical piece of evidence was a week late in getting into my hands and so the State Department has 5 business days plus Saturday to get my passport to me. *gulp* Good thing I asked for expedited service.. I know they received my application on the 13th at midday in Philly. Should be enough time (she tells herself…).

Anyways.

Once I get back to England I will likely inherit Anne’s laptop which will be put to UO usage so my desktop can return to its Linux glory cos frankly Windows is irritating.

I’ve got lots of motivation and really want to (finally) test SLP support in Distcc. I’ll have to set up Hydrogen (our fileserver) to use the correct toolchain as Lithium (my desktop) and Helium (our general purpose server box) to have matching configs for glibc, distcc, and gcc. Fun! 😉

okay
in the past i’ve made references to surgery… my fiancee and i registered a domain http://www.helpmyfiancee.com please read and pass it on.

thank you

if anyone has questions pm me on irc.

In 3 years, 200 days, 23 hours, and 39 minutes Gentoo got 100.000 bugs.
That’s 77.1613620909 bugs per day.
The first bug on record is How do I attach an ebuild. (at 2002-01-04 02:39 PDT) and the 100.000th is clanlib 0.7.8-r1 can’t emerge (xargs: environment is too large for exec) (at 2005-07-23 03:18 PDT). As of this post we are up to 100.109 bugs. The off-by-one in the counting is because the first bug is #2. And as we all know 100.002-2 = 100.000!

I wonder how many of these are due to people using crazy CFLAGS?

Edit: Random wanker Daniel Hancock’s comment is deleted and his IP is 218.101.84.118 for future reference.