X-Win32 Knowledge Base   >   bash: No such file or directory

Search


About StarNet

StarNet Communications has been a leading developer of X Windows solutions since 1989. After establishing X-Win32 as the de facto standard in the higher education market during the early to mid-1990s -- 150 unlimited Campus Site Licenses worldwide -- X-Win32 has become of one the top three PC X servers in the government and commercial sectors as well.

Unlike its major rivals, Exceed (Hummingbird) and Reflection-X (WRQ/Attachmate), X-Win32 offers a highly focused PC X server that offers superior performance and productivity features, stability, ease of use and low cost (40% or better in most cases).

StarNet also delivers unequaled customer support. Our state-of-the-art engineering infrastructure allows us to fix problems and make a new release available quickly (overnight in many cases). As our testimonials page shows, StarNet customers consistently rate their X-Win32 experience as the best in the industry.




bash: No such file or directory

If you see an error similar to one of the following, then it means that the remote system cannot find the program that you are trying to run on the remote system:

  • bash: line 1: /usr/X11R6/bin/xterm: No such file or directory
  • xterm: No such file or directory
  • dtterm: No such file or directory
  • /usr/bin/xterm: No such file or directory

    This error usually results because the path to the command is incorrect.

    Typically, our users will start a terminal (e.g. xterm, dtterm, konsole, gnome-terminal) as the program that is run by their X-Win32 session, then they will start the programs that they actually want to use from this terminal (e.g. ‘mozilla &’, ‘firefox &’, ‘oowrite &’, etc.). If you are starting a terminal from your X-Win32 session, then we have steps below to help you find the location of the terminal program that you are trying to run. However, if you are directly starting another application from your X-Win32 session, then you may want to consult your system administrator or use the steps below only as helpful tips to use in locating your application.

    If you do not know the location of the remote terminal command, then try the following trouble shooting steps:

    1. Remove the full path from the command, that is, try setting the session command to xterm instead of /usr/X11R6/bin/xterm. Many Linux systems (e.g. Red Hat, SuSE, Ubuntu, Debian, etc.) ship with their terminal programs in the path, so specifying xterm as the command usually just works.
    2. If you are connecting to a Solaris machine, try starting dtterm instead of xterm. dtterm is generally present on Solaris, while xterm may be optional or in a strange location.
  1. If you simply cannot find the location of xterm, then use find to help you. Change your session command to find / -maxdepth 3 -name xterm 2>/dev/null, then check the Show Messages box on your session. When run, this session will cause the Messages window to open, and will show output similar to that below. The output below shows that xterm is located at /usr/bin/xterm, so you can change your session command to /usr/bin/xterm -ls [...] and it should work.

    Sample output from using find as a session command

    find: /dumps/lost+found: Permission denied<br>
/usr/bin/xterm

    Category:Errors
    Category:Sessions



How Can We Improve This KB Article?

Please rate the quality of this article: Excellent Good Fair Poor

Did this article answer your question? If not, we'd like to hear more about it:

Do you need additional assistance? If so, enter your email address:

Articles are periodically updated based on your feedback. If you enter an email address, then you will be given the opportunity to open a case, for which you will receive a response within 2 business days.