named-xfer problem w/chroot on Solaris (very long)
Mark.Andrews at nominum.com
Mark.Andrews at nominum.com
Wed Aug 1 21:42:53 UTC 2001
> Ian Watts <ian at radix.net> wrote:
>
>
> > I can't say that I studied your message as carefully as I might have, but
> > the files that I included on my Solaris 8 boxes for running chroot'ed also
> > include:
>
> > ld.so.1
> > libl.so.1
>
> > in addition to what you mentioned:
>
> > libc.so.1 libmp.so.2
> > libdl.so.1 libnsl.so.1
> > libld.so.2 libsocket.so.1
>
> > It certainly could prevent the transfers. Copy them to your usr/lib
> > directory and try again.
>
> Thanks, Ian. My message is lengthy, I'm glad you skipped it. I put in
> all the detail that I thought anyone would need both to answer and make
> it worth an archive search.
>
> Your answer does indeed solve the problem.
>
> Also, this advice is given on the web pages commonly found to have
> chroot instructions (the Sun World arts, et al.).
>
> However, my system (SunOS 5.6) does not seem to have libl.so.1 -
> seems Ok without it.
>
> You would think it anybody in posession of one good brain cell would
> reckon that "dynimcally linked" executables would need to link do
> the dynamic loader library. For some reason, it being very very
> late at night, I had figured that ld.so had a "lib" prefix on it...
> and the only one I saw was libld.so.2... plain old wrong thinking.
>
> Thanks again! Lesson: after sleep, don't try to continue the previous
> night's unorganized problem solving: start all over in the morning.
>
> --
>
> Silverman's Law:
> If Murphy's Law can go wrong, it will.
>
You should also note that the ftpd man page is usually a good
starting point for setting up a chroot envirionment as named-xfer
needs at least what ls needs to run in a chroot envirionment.
Mark
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at nominum.com
More information about the bind-users
mailing list