On Thu, Mar 02, 2006 at 04:02:37PM -0800, Jonathan Adams wrote: > On Thu, Mar 02, 2006 at 04:00:46PM -0800, Edward Pilatowicz wrote: > > On Thu, Mar 02, 2006 at 11:16:14AM +0000, Darren J Moffat wrote: > > > Edward Pilatowicz wrote: > > > >suggestions? (a recommendation to get my head check could be > > > >a valid suggestion.) > > > > > > Other than use a Zone instead of a chroot ? Assuming you can. > > > > > > > i'm already in a zone. > > > > > Why is the application doing a chroot anyway ? > > > > > > > because it's much cleaner than doing pathmapping. ;) > > > > this is for brandz and the application is a solaris daemon running in > > a linux branded zone. > > Why not just execute: > > /sbin/chroot /a /bin/to/run >
short answer: because life isn't as simple as it should be. long answer: in certain cases the application needs access to the real root filesystem, so when it starts up i open "/" so i have a fd pointing to it before i call chroot(). the good part is that i've got a decent workaround in place for now. ed
