Re: Obscure IO::Socket poop under a chroot Help Help Help!

Didn't realize it was this simple:

[code 16:02] Dorn :) http://www.perlmonks.org/index.pl?node_id=181126.

[code 16:03] Arren@Anarres II: Ohhhhhh.
[code 16:03] Arren@Anarres II: Now I see the trace, it's obvious.
[code 16:04] Arren@Anarres II: getprotobyname is a C library call whic
+h reads /etc/protocols, which is not available in your
chroot.
[code 16:04] Arren@Anarres II hits himself with a stick.
[code 16:04] CyberTiger@Anarres II slaps Arren@Anarres II. (from Cyber
+Tiger@Anarres II)
[code 16:04] CyberTiger@Anarres II: yoou shoulda known that :P.
[code 16:04] Arren@Anarres II: Thankyou. I suck goats off for fun. But
+ that's the problem.
[code 16:05] CyberTiger@Anarres II: don't get yourself confused with A
+l.
[code 16:05] Arren@Anarres II: You might be able to just use 6 instead
+ of 'tcp'.
[code 16:06] CyberTiger@Anarres II: so turn /etc/protocols into a #def
+ine, there's a #define for the protocol number for tcp
anyway.
[code 16:07] Arren@Anarres II hits CyberTiger. 1. This is Perl. 2. The
+ number for TCP isn't going to change this week. 3. What? 4.
[download]

Comment on Re: Obscure IO::Socket poop under a chroot Help Help Help! Download Code

Replies are listed 'Best First'.
Re: Re: Obscure IO::Socket poop under a chroot Help Help Help! by ferrency (Deacon) on Jul 11, 2002 at 20:28 UTC
If you want to be extremely anal about this, you could do your own `getprotobyname` before you `chroot()`, and use the value it returns instead of hardcoding a "6" (or whatever). It may not make sense for your particular application, but you may also be able to open your listening socket first, and then chroot. Alan	[reply] [d/l] [select]