Michael Smith wrote:> As you've found out, you do need a lot of stuff on modern systems (you > didn't say what OS you were using, though) to get a working resolver.Grumpf. Linking is a fine thing for space economy, but for chroot I wish everything was static and monolithic and self-contained.> You should be able to find some info with a web search - just don't > make it icecast-specific...That's a very good idea indeed; I was focusing too much on icecast itself. There should be a chroot package, just like the one Redhat makes for bind. If I manage to solve this, I might take a shot at packaging the solution. BTW, the OS is Linux, RHEL3-flavour. I'd assume every *nix has the same problem though. Karl Heyes wrote:> If these modules are loaded after the start of icecast (the default case > on linux) and more specifically after the chroot then these also have to > be in the chroot jail as wellIndeed. I'll try the simple things to begin with. If they don't work, strace might tell me what's missing in the chroot. It amazes me though that nobody has run into this before. Z -- The best defence against logic is ignorance.
On Sun, 2005-01-23 at 03:22, Zenon Panoussis wrote:> Michael Smith wrote: > > > As you've found out, you do need a lot of stuff on modern systems (you > > didn't say what OS you were using, though) to get a working resolver. > > Grumpf. Linking is a fine thing for space economy, but for chroot > I wish everything was static and monolithic and self-contained.if you have the build environment and the source tree then a make static should work karl.
On 23 Jan 2005 03:33:37 +0000, Karl Heyes <karl@xiph.org> wrote:> On Sun, 2005-01-23 at 03:22, Zenon Panoussis wrote: > > Michael Smith wrote: > > > > > As you've found out, you do need a lot of stuff on modern systems (you > > > didn't say what OS you were using, though) to get a working resolver. > > > > Grumpf. Linking is a fine thing for space economy, but for chroot > > I wish everything was static and monolithic and self-contained. > > if you have the build environment and the source tree then a make static > should work > > karl. >Except "make static" will helpfully build you a statically linked icecast which still dynamically loads modules for the name service (via nsswitch.conf, as you noted). Yes, that's right: on a modern linux system (as far as I know), there is no way to build a fully statically linked application which can do hostname lookups. This can be rather a pain... Mike
Zenon Panoussis wrote:> It amazes me though that nobody has run into this before.People have. And I vaguely recall someone doing some work indetermining all that was needed and wrote to the list about it. I usually keep such messages, but can't find it right now. But yes, I've seen about 3 or 4 separate queries about this issue. Geoff.