Re: [IBMiOSS] Using Nodev6 db2i/itoolkit

I noticed the original documentation calls for chown -R where the

chroot_chown.sh uses chown -Rh; would that make a difference?

Yes, you should change the owner to that of the developer who will use it.
With that said, you need *ALLOBJ to enter into a chroot. If that's not
possible then you can change your HOMEDIR on your profile to be
'/QOpenSys/ibmichroot_containers/gallmanm/./home/GALLMANM'. Notice the
period; that's required and is what causes your inbound ssh session to be
chroot'd to that location.


​​
Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces


On Fri, Mar 30, 2018 at 11:47 AM, Mitch Gallman <mitch_gallman@xxxxxxxxxxxxx

wrote:

Progressing...

Yes, still running in QSH. I am working on getting SSH access now
(currently we aren't even running the SSH server). I've had git
bash...just have to go through the proper authorites.

As you noted I wasn't running from bash and was hitting the file
descriptor limit of 200. When running in bash from the green screen it ran
successfully.

However, now when I'm trying to use it I get the following:

chroot /QOpenSys/ibmichroot_containers/gallmanm /QOpenSys/bin/bsh

/QOpenSys/ibmichroot_containers/gallmanm: The file access permissions do
not allow the specified action.
$

I noticed the original documentation calls for chown -R where the
chroot_chown.sh uses chown -Rh; would that make a difference?

Running on V7R2.

Mitch Gallman