Has anyone successfully invoked qsh, qsh_out or qsh_inout from the ssh terminal?
yl_mra
Software ISeries PASE news group. To date, no one has responded to
that post.
PASE was factory installed on our V5R3M0 and V5R4M0 systems and works
great. A few weeks ago, I followed the IBM instructions and set up the
jobd, sbs, etc. just as directed. All works fine except that invoking
qsh via the PASE shell from the ssh terminal fails. I see the same
behavior on both i5 systems from either a standard Linux terminal
under ubuntu or PuTTY under Windows XP. Invoking qsh from pase started
via QP2TERM works as documented and using a system call to qsh from
the ssh terminal works fine.
IBM documentation and a number of other sources indicate that qsh
works when invoked from the pase shell using ssh terminal access. For
test purposes, I have invoked ssh via the jobd, as documented, using
both qsh and QP2SHELL. Both ways are documented in separate documents
and both appear to work equally well. I also set the environmental
variables as documented and I also set them as they are set when
QP2TERM is used.
Has anyone successfully invoked qsh, qsh_out or qsh_inout from the ssh
terminal?
Mike
Only specific PTFs have been applied since purchase of the system
V5R3. This system is intentionally maintained at a down level. The
latest CUM PTF package on the V5R4 system is C7226540.
iseriesflorida
yl_mra
After reviewing the referenced document, it does not seem to help as
the method for starting the ssh manager remains the same. I think that
the problem lies in the need to use QP2SHELL as noted in
http://www-912.ibm.com/s_dir/slkbase.NSF/643d2723f2907f0b8625661300765a2a/83f6d4269d9ebdc786257043005ac2ab?OpenDocument
This is why I asked if anyone had successfully invoked qsh via ssh; if
so, then I can find a reference from which to work.
Of course, one can still invoke qsh via a system call; however, the
return code is from system, not qsh, and the output is not clean.
Mike
P.S. I also checked the PTF list to see if any would affect this
particular problem.
yl_mra
newsgroup on news.software.ibm.com.
> > Has anyone successfully invoked qsh, qsh_out or qsh_inout from the ssh
> > terminal?
How are you starting sshd? Using CL, you should start sshd with
something
like this:
QSH CMD('/usr/sbin/sshd')
I have seen instructions that say to start sshd with QP2SHELL and
this
can/will cause problems due to the ILE file descriptors for stdout
and
stderr being inherited from the parent process that invokes QP2SHELL
into
the forked sshd child processes. Using QSH (or QP2TERM) will create
inheritable/forkable stdout and stderr descriptors for the sshd
process.
--
-----
Walt Madden
IBM i software development
==============================================
I in turn responded:
Walt Madden wrote:
> How are you starting sshd? Using CL, you should start sshd with something like this:
> QSH CMD('/usr/sbin/sshd')
>
Thank you Walt. This does work and it works using both path '/usr/sbin/
sshd' and 'QOpenSys/usr/sbin/sshd'. Both paths link to the same
executable, /QIBM/ProdData/SC1/OpenSSH/openssh-3.5p1/sbin/sshd.
The following documents should be reviewed and modified as they
instruct users to use QP2SHELL.
Example application - SSH
http://www-03.ibm.com/servers/enable/site/education/wp/7f4a/page_4.html
OpenSSH: How to Stop SSH from Creating Thousands of Job Logs
http://www-912.ibm.com/s_dir/slkbase.NSF/643d2723f2907f0b8625661300765a2a/83f6d4269d9ebdc786257043005ac2ab?OpenDocument
RedPaper
Securing Communications with OpenSSH on IBM i5/OS, July 2006
The document 'Qshell and OpenSSH for IBM System i' by Bob Bittner
dated 15-May-2007, appears to be correct.
Mike Amos
yl_mra
Mike Amos