Xref: utzoo comp.unix.admin:46 comp.unix.questions:25323
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ncar!mephisto!prism!gt0178a
From: gt0178a@prism.gatech.EDU (BURNS,JIM)
Newsgroups: comp.unix.admin,comp.unix.questions
Subject: Re: help removing a file
Message-ID: <13419@hydra.gatech.EDU>
Date: 7 Sep 90 03:23:35 GMT
References: <1212@tardis.Tymnet.COM>
Followup-To: comp.unix.admin
Distribution: usa
Organization: Georgia Institute of Technology
Lines: 15

in article <1212@tardis.Tymnet.COM>, jms@tardis.Tymnet.COM (Joe Smith) says:
> The reason that works is because an executable script that does not start
> with "#", "#!/bin/xxx" or ":" is executed by /bin/sh instead of your default
> shell, 

Not on any system I've worked on. It always defaults to $SHELL, your
current shell. If this wasn't true, I couldn't use ksh aliases and
functions inside my scripts w/o #!/bin/ksh (or whatever). If what you mean
is that *csh* defaults to /bin/sh w/o one of your constructs, this is
true.
-- 
BURNS,JIM
Georgia Institute of Technology, Box 30178, Atlanta Georgia, 30332
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt0178a
Internet: gt0178a@prism.gatech.edu