home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!math.fu-berlin.de!unidui!Germany.EU.net!incom!orfeo!qb!vhs
- From: vhs@rhein-main.de (Volker Herminghaus-Shirai)
- Subject: Re: Exec. files not being fd
- Message-ID: <1993Jan2.193657.3017@qb.rhein-main.de>
- Sender: vhs@qb.rhein-main.de (Volker Herminghaus-Shirai)
- Reply-To: vhs@rhein-main.de
- References: <72576@cup.portal.com>
- Date: Sat, 2 Jan 93 19:36:57 GMT
- Lines: 29
-
- In article <72576@cup.portal.com> John-Z@cup.portal.com (John Michael
- Zollinger) writes:
- > Help...For some reason my shell can't find executable files. If I
- > compile a little C program and then rehash (I am doing that), it still
- > says that it can't find the file, even though 'ls' shows that it is
- > there. In addition, adding entries to my PATH setup in the shell startup
- > script doesn't seem to have any effect, but if I put an executable file
- > into the standard path, like '~/Unix/bin/' it finds it ok.
- >
- > As you can see, I am at a loss as to what is wrong so any help would be
- > greatly appreciated. Thanks.
-
- First find out definitely what shell you are using. Then, make sure
- you use the right startup script, i.e. .profile for sh, .cshrc
- for csh, etc.
- Do a `which rehash` to find out if some buzzhead wrote a no-op,
- named it rehash, and put it into the path. Output should be:
- no rehash in <your_path>
-
- I can't think of another reason right now except if your filesystem
- or shell is seriously broken. If the above doesn't help try using sh
- and csh alternatively and check if it happens on both. Also try
- invoking the executable directly, i.e. ./myprog, or ./bin/myprog.
-
- --
- Volker Herminghaus-Shirai (vhs@qb.rhein-main.de)
-
- Looks good on the outside, but -
- intel inside
-