Reflection X - xtem HP-UX 10.20

[Tania Ap. Serpa Martins]

I have one account that its .profile call the menu in the script bourne-shell. That is running very well in a DVX X-emulator. But I try to use with Refletion X and the script not show the window, but it is running and I could observe that it fork the process that is the same script.

ex: .profile

exec /lbin/menu/operation.sh

-> Command in reflection X in TELNET MODE:
(/usr/bin/X11/xterm -fn 6x13 -sb -ls -display IP:0 &)

-> When I started without a line "exec /lbin/menu/operation.sh" and after call the command with exec, that works fine.

Could someone help me, please?

[Enrico P.]

Hi,
I don' t now if it work but you can try with:

(/usr/bin/X11/hpterm -fn 6x13 -sb -ls -display %IP#% -name %T% &)

Enrico.

[Tania Ap. Serpa Martins]

Enrico,

I've tried to use that you mentioned. And the problem persists.

Thanks

[doug mielke]

Here are the two that I use, first is for the hp specific term type;


(/usr/bin/X11/hpterm -fn 6x13 -sb -ls -display %IP#% -name %T% &)



(/usr/bin/X11/xterm -fn 6x13 -sb -ls -display %IP#% -name %T% &)

[Tania Ap. Serpa Martins]

Doug,

That is works fine with I comment the line :

"exec /lbin/menu/operation.sh" - script that is a menu wrote in bourne-shell.

The problem is when this line will be executed from .profile.

[Enrico P.]

Hi,
try to launch the script without "exec", es put in your .profile the line:

/usr/bin/sh /lbin/menu/operation.sh

Enrico.

[Enrico P.]

Hi,
from the reflection X guide:
Does your login shell start another program, or are you running programs in the background?

Some UNIX hosts will suspend a process if there is no standard out (STDOUT) or standard error (STDERR) associated with it, or if a process is started in background. In these cases, there is no "controlling tty."
For example, let's say you are connecting to a UNIX host and using the Bourne shell. When you log in, the Bourne shell looks for a file called .profile in your home directory. If .profile includes a command to start another application, such as an editor, the editor can't write to STDOUT because the process was started remotely. You can, however, always write to /dev/null. Redirect the STDOUT and STDERR of the editor to /dev/null in the directory from which the editor is started:

editor >/dev/null 2>&1 & (for the Bourne and Korn shells)
editor >& /dev/null & (for the C shell)

?? 1993-1996 WRQ, Inc.

Enrico