Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!sdd.hp.com!elroy.jpl.nasa.gov!turnkey!jackv
From: jackv@turnkey.tcc.com (Jack F. Vogel)
Newsgroups: comp.unix.i386
Subject: Re: BUG in ISC UNIX 2.2
Keywords: bug, exec, isc, unix, 386/ix
Message-ID: <1990Jul2.155159.664@turnkey.tcc.com>
Date: 2 Jul 90 15:51:59 GMT
References: <1990Jun30.212356.1209@virtech.uucp>
Reply-To: jackv@turnkey.TCC.COM (Jack F. Vogel)
Organization: Turnkey Computer Consultants, Westchester, CA
Lines: 24

In article <1990Jun30.212356.1209@virtech.uucp> cpcahil@virtech.uucp (Conor P. Cahill) writes:
>Although I can't find it documented anywhere, ISC has apparently added
>support for exec(2) interpretation of the "#!interpreter" line at 
>the begining of a script file.  This works pretty well until you give
>it a name that is longer than 18 bytes.
 
Conor, really, I am surprised at you :-}, not reading the release notes on
a new release! I quote from page 12:

	The exec(2) system call has been enhanced to allow script files to
	be interpreted by a shell (or command interpreter) of the writers
	choice. To take advantage of this feature, a script must include
	the line #! interpreter, where interpreter is any command processor,
	such as /bin/csh...

In any case, thanks for the info on the related bug, have you informed ISC
of this other than assuming they track things posted here??

Disclaimer: I speak for myself, not my employer.

-- 
Jack F. Vogel			jackv@locus.com
AIX370 Technical Support	       - or -
Locus Computing Corp.		jackv@turnkey.TCC.COM