Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal L. Schwartz)
Newsgroups: comp.unix.questions
Subject: Re: Problem with #!
Keywords: scripts expect
Message-ID: <1990Dec24.015805.18447@iwarp.intel.com>
Date: 24 Dec 90 01:58:05 GMT
References: <1990Dec23.083329.22021@csn.org> <1990Dec23.232842.4354@virtech.uucp>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal L. Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 21
In-Reply-To: cpcahil@virtech.uucp (Conor P. Cahill)

In article <1990Dec23.232842.4354@virtech.uucp>, cpcahil@virtech (Conor P. Cahill) writes:
| The problem is that the kernel is interpreting the #! and it (the kernel)
| has a fixed limit on the number of bytes (I have seen it as low as 32 bytes).
| 
| The solution is to put expect in a public place with a shorter
| path, or use symbolic links to make the path shorter.

Amazingly enough, symbolic links *won't* help on anything as early as
Ultrix 4.0 (it may be fixed in Ultrix 4.1).  Apparently, the
*expanded* name (what the symlink is linked to) has to also fit within
the 32(!) character limit.  Blech.  SunOS is not so braindamaged...
the 32-char limit applies only to the original text after the #! line.

And why the number has to be so small (like 32 chars) is beyond me.

Just another Unix hacker,
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Intel: putting the 'backward' in 'backward compatible'..."====/