Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: #! on Ultrix
Message-ID: <1990Jul16.175554.28208@iwarp.intel.com>
Date: 16 Jul 90 17:55:54 GMT
References: <1990Jul16.162054.10019@uvaarpa.Virginia.EDU>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 30
In-Reply-To: worley@compass.com (Dale Worley)

In article <1990Jul16.162054.10019@uvaarpa.Virginia.EDU>, worley@compass (Dale Worley) writes:
| 
|    X-Name: Randal Schwartz
| 
|    Thus, I presume you ran into the stupid stupid problem
|    that I did... that symlinks in the command name are *expanded* *within*
|    that 32-char limitation *only* under Ultrix!  Gack!
| 
| Gag me with a VAX!  How can the kernel handle symlinks correctly for
| ordinary file opens and screw it up for #!s???

It does, and it still does under 3.1 (we tested it after I posted).
They probably don't even know of it as a problem yet.  (They would
probably just give me a workaround anyway: "put your files in
directories with shorter names".  Yuck.)  As I said, Ultrix is not
UNIX (but closer than HP-UX or AIX, apparently).

Without testing I'd venture a guess that the symlink expansion is also
happening for ordinary file lookups, which means you could run out of
a buffer there too, although the buffer is probably 1K or larger.  32
bytes is pretty tight.

But what does this have to do with Perl now?  Probably not much.

Just another UNIX hacker with a Perl bent,
-- 
/=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: "Welcome to Portland, Oregon, home of the California Raisins!"=/