Upshot and Nupshot
Up: In case of trouble Next: General Previous: Workstation Networks
The upshot and nupshot programs require specific versions of the tcl and tk languages. This section describes only problems that may occur once these tools have been successfully built.
Up: In case of trouble Next: General Previous: Workstation Networks
General
Up: Upshot and Nupshot Next: HP-UX Previous: Upshot and Nupshot
-
1. Q:
When I try to run upshot or nupshot, I get
No display name and no $DISPLAY environment variablesA: Your problem is with your X environment. Upshot is an X program. If your workstation name is "foobar.kscg.gov.tw", then before running any X program, you need to do
setenv DISPLAY foobar.kscg.gov.tw:0If you are running on some other system and displaying on foobar, you might need to do
xhost +othermachineon foobar, or even
xhost +which gives all other machines permission to write on foobar's display.
If you do not have an X display (you are logged in from a Windows machine without an X capability) then you cannot use upshot.
2. Q:
When trying to run upshot, I get
upshot: Command not found.A: First, check that upshot is in your path. You can use the command
which upshotto do this.
If it is in your path, the problem may be that the name of the wish
interpreter is too long for your Unix system. Look at the first line of the
upshot file. It should be something like
#! /usr/local/bin/wish -fIf it is something like
#! /usr/local/tcl7.4-tk4.2/bin/wish -fthis may be too long of a name (some Unix systems restrict this first line to a mere 32 characters). To fix this, you'll need to put a link to wish somewhere where the name will be short enough. Alternately, you can start upshot with
/usr/local/tcl7.4-tk4.2/bin/wish -f /usr/local/mpi/bin/upshot
Up: Upshot and Nupshot Next: HP-UX Previous: Upshot and Nupshot
HP-UX
Up: Upshot and Nupshot Next: Appendices Previous: General
-
1.
Up: Upshot and Nupshot Next: Appendices Previous: General