[7891] in SIPB bug reports
[Fwd: "ruby" interpreter symlink can be dangling]
daemon@ATHENA.MIT.EDU (Jacob Morzinski)
Tue Dec 18 18:51:35 2001
Message-ID: <3C1FD66B.1090503@mit.edu>
Date: Tue, 18 Dec 2001 18:51:07 -0500
From: Jacob Morzinski <jmorzins@MIT.EDU>
MIME-Version: 1.0
To: Alex Coventry <alex_c@MIT.EDU>
CC: bug-sipb <bug-sipb@MIT.EDU>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Alex doesn't appear to be on bug-sipb, so I'm forwarding the other
Alex's message.
(I personally agree that it's good to be able to run a scripting
language without attaching the locker. Another way to resolve the
issue, though, would be to use a relative symlink.
ln -s arch/@sys/bin bin , repeat for other links.)
-------- Original Message --------
Subject: "ruby" interpreter symlink can be dangling
Date: Tue, 18 Dec 2001 18:35:03 -0500
From: Alex T Prengel <alexp@MIT.EDU>
To: bug-sipb@MIT.EDU
CC: alexp@MIT.EDU
Hi, I was playing with ruby and noticed that the link:
/afs/sipb/project/ruby-lang/bin -> /mit/ruby-lang/arch/@sys/bin
will be dangling if the ruby-lang locker is not attached. Wouldn't it
be better to use a /afs/... path instead of a /mit/... path in such a
case? I don't think you should need to do an "attach" before
executing an executable script in a scripting language...
Alex
