FGLTTY hanging when running autoportfind

"Michael Laporte" <[email protected]> Mon, 11 Sep 2006 15:27:09 -0400
Newsgroups gmane.comp.lang.4gl.fourjs.user
Message-ID <[email protected]>
------=_Part_6992_1769244.1158002829359
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

We are having problems where the initial FGLTTY program hangs when
attempting to run the autoportfind command (we are running the GDC over an
automatically assigned tunneled port).  I have tracked it down to when the
autoportfind program tries do display the port it found to the screen.
Replacing the autoportfind command with a simple "echo" command in the GDC's
Automatic (specify the command) field generates the same result.  The
process is somehow in a sleep state and not waking up to display the value.
Our workaround has been to change the specified command from
"/usr/local/bin/autoportfind -e" to "/usr/local/bin/autoportfind
-e;/bin/ksh".  For some reason, the call to run the Korn shell causes the
process to wake up and finish processing. After the shell is run, the FGLTTY
finishes up (so we don't have to issue the exit command) and continues on
happily.

The odd thing is that without the workaround, the problem is sporadic in
that sometimes it works properly, but most times it does not.  With the
workaround, it always seems to work fine.

We have only noticed this particular problem against AIX machines (4.3.3,
5.1, 5.3), but with many different versions of the GDC.

Has anyone else run into this particular problem before?  Does anyone have
any insight as to what the "real" problem may be?

Thanks,

-- 
Michael Laporte

------=_Part_6992_1769244.1158002829359
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

We are having problems where the initial FGLTTY program hangs when attempting to run the autoportfind command (we are running the GDC over an automatically 
assigned tunneled port).&nbsp; I have tracked it down to when the autoportfind program tries do display the port it found to the screen.&nbsp; Replacing the 
autoportfind command with a simple &quot;echo&quot; command in the GDC's Automatic (specify the command) field generates the same result.&nbsp; The process is 
somehow in a sleep state and not waking up to display the value.&nbsp; Our workaround has been to change the specified command from 
&quot;/usr/local/bin/autoportfind -e&quot; to &quot;/usr/local/bin/autoportfind -e;/bin/ksh&quot;.&nbsp; For some reason, the call to run the Korn shell causes 
the process to wake up and finish processing. After the shell is run, the FGLTTY finishes up (so we don't have to issue the exit command) and continues on happily.
<br><br>The odd thing is that without the workaround, the problem is sporadic in that sometimes it works properly, but most times it does not.&nbsp; With the 
workaround, it always seems to work fine.<br><br>We have only noticed this particular problem against AIX machines (
4.3.3, 5.1, 5.3), but with many different versions of the GDC.<br><br>Has anyone else run into this particular problem before?&nbsp; Does anyone have any 
insight as to what the &quot;real&quot; problem may be?<br><br>Thanks,<br clear="all">
<br>-- <br>Michael Laporte

------=_Part_6992_1769244.1158002829359--