× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks Wayne. I invoked it as you recommended and it works!

Stick a "fork" in it. It's done.

Pete


Walt Madden wrote:
Pete Helgren wrote:
For example, java -version in QSH and QP2TERM
produce: java version "1.4.2". In pUTTY, nothing is output. Not
even an error.

If you used QP2SHELL (versus QSH or QP2TERM) to start sshd you can see this behavior. This is due to differences between the way QP2SHELL runs the specified program (sshd in this case) versus the way QSH and QP2TERM run the program.



Since QP2SHELL runs the program in the same process that is calling QP2SHELL, the program started by QP2SHELL inherits the ILE file descriptors for stdin, stdout and stderr that existed in the process calling QP2SHELL. These ILE descriptors can be unreliable when used in an environment that uses the fork() API (and sshd is such an environment).



Contrast with QSH or CALL QP2TERM -- these both will create a new process to run the specified program in and they both set up that new process with true IFS stream file descriptors for stdin, stdout and stderr. These IFS descriptors are "forkable".



So. Try something like this to start sshd and see if it doesn't improve things for you:

QSH CMD('/QOpenSys/usr/sbin/sshd')



-- Walt Madden





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.