>>> Yeah, I created a node and still get internal error #11 when
 >>> starting.  To avoid permission issues, I'm testing this under the
 >>> superuser account.

 AI>> I've seen that too in the linux version. In the irex .pdf it says that
 AI>> error 11 is probably a bug in irex, but I don't know what it means for
 AI>> sure. I could run ./rexl -send -fetch on my debian box and irex worked
 AI>> as expected, but when I tried to run -daemon I would get error 11.

 GKA> THe problem in irex linux is that many people there using
 GKA> linux has got this error and irex linux not like using
 GKA> directly hostnames lookup and poll it. to solve this error is
 GKA> there a way to resolve it is it to set irex to lookup hostname
 GKA> off and then use ip addreses instead of hostnames until
 GKA> Charles has manage to make a new vesion of irex there has
 GKA> fixed the problem.

this is all due to a change in the way that DNS lookups are done in
linux... i remember when the change happened but not with what version of
the linux kernel... my memory wants me to write that v2.4.xx of the kernel
is ok but those after that have the problem... so all it would take would
be to recompile IREX on a newer system to fix the problem... i do not
believe that there would need to be any actual code changes but i have not
dug into it any deeper... IREX is not the only software that has/had this
problem... in all cases that i'm aware of, it only took recompiling the
code on a box with the newer kernel and headers to fix this particular
problem...

)\/(ark