Article View: comp.sys.sgi.misc
Article #148Re: strange problem with command execution at xwsh startup
From: Kipp Hickman
Date: Tue, 05 Jan 1993 21:37
Date: Tue, 05 Jan 1993 21:37
19 lines
1216 bytes
1216 bytes
In article <1ictqqINNk4a@tamsun.tamu.edu>, vamsee@abgen.tamu.edu writes: > %xwsh -e rlogin <any-host> > > The above command works on this SGI (Indigo 4.0.5A). But, > > %xwsh -e /bin/ls This will work, it just exit's immediately after finishing. Try adding the "-hold" option if you want wsh to hang around after finishing monitoring the subprocess. > %xwsh -e cd /usr/people/vamsee/junk > %xwsh -e chdir /usr/people/vamsee/junk > %xwsh -e cd /usr/people/vamsee/junk; vi <somefile> These will never work because there is no such program called "cd". When you give xwsh the "-e" option you are changing its notion of the shell to use to a specific program. The arguments you give are just exec'd, not run through another shell. kipp
Technical Details
Message-ID:
<1icv27INN6f2@fido.asd.sgi.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!olivea!sgigate!sgi!fido!warp!kippReferences:
<1ictqqINNk4a@tamsun.tamu.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!sgigate!sgi!fido!warp!kipp From: kipp@warp.asd.sgi.com (Kipp Hickman) Newsgroups: comp.sys.sgi.misc,comp.sys.sgi.apps,comp.sys.sgi Subject: Re: strange problem with command execution at xwsh startup Message-ID: <1icv27INN6f2@fido.asd.sgi.com> Date: 5 Jan 93 21:37:11 GMT References: <1ictqqINNk4a@tamsun.tamu.edu> Organization: Silicon Graphics, Inc. Mountain View, CA Lines: 19 NNTP-Posting-Host: warp.asd.sgi.com