My question follows the summary.
Thanks to all, including:
Lawrence Decker
Chad Price
Richard Eisenman
Who suggested redirecting the output to files. Unfortunately, this wasn't an
option, since these programs interact, and we wish to observe these
interactions. Sending the outputs to files it would be impossible to tell
what was happening and when, unless we modified the programs to timestamp
the outputs. Also, in production these output will be closely monitored.
Also thanks to:
Massimo Gais
Robert Mulley
Jim Belonis
Micono, Jeff
Frank Wortner
Phil Farrell
John P Speno
Roy Marcus
Nick M
Ronald D. Bowman
Dr. Tom Blinn
Anthony A. D. Talltree
Sean O'Connell
Oisin McGuinness
Who all suggested wrapping the programs in a script with a read or sleep at
the end then starting the script inside the "xterm -e" command. This would
keep the xterm window open until the end of the sleep or until the enter key
was pressed. I did this and sent it to the developer as one option.
Special thanks to:
Paul Henderson
Who introduced me to the "dxdw -c" command. It opens an X window that not
only stays open after the command exits but it saves the command line and
lets your restart it from the same X window. It also has a button to stop
the command, again without exiting from the window. It even had a button to
repeat the command at a specified interval.
The only drawback was it didn't use the command name for the window title.
It does recognize some xterm options like -bg, -fg and -n but the -T option
was not recognized and returned a usage error. But since the command line
running appears in the window this is not a serious drawback. This was the
option most favored.
Additional thanks to:
Ardizzoni Enrico
Who suggested using the nohup command to launch the xterms. I haven't had a
chance to test this yet, but plan on giving it a try.
-----Original Message-----
From: tru64-unix-managers-owner_at_ornl.gov
[mailto:tru64-unix-managers-owner_at_ornl.gov] On Behalf Of Jim Fitzmaurice
Sent: Tuesday, September 28, 1999 12:35 PM
To: Tru64 -unix -managers
Subject: UPDATE: Quick xterm -e question
Hello again,
I'm getting responses, but after reading them I'm afraid I wasn't clear in
what I was looking for so let me re-phrase that.
My developer has a script:
#!/bin/sh
<setup environment>
<program> &
<program> &
<program> &
This overflows his termial with output so he wants to put each program in it
own xwindow. I suggested "xterm -e <command>" so now the script reads:
#!/bin/sh
<setup environment>
xterm -e <program> &
xterm -e <program> &
xterm -e <program> &
This works fine except if a program exits, the xterm window disappears. That
means if it exits with an error, you don't see the error. How can I keep the
xterm window open after the program exits? If it's even possible.
Jim Fitzmaurice
jpfitz_at_fnal.gov
UNIX is very user friendly, It's just very particular about who it makes
friends with.
Received on Wed Sep 29 1999 - 15:39:17 NZST