From: lat AT iki DOT fi (Lassi A. Tuura)
Subject: Re: AFS executable problems
26 Sep 1998 00:06:14 -0700
Message-ID: <Pine.HPP.3.95a.980925154431.6772R-100000.cygnus.gnu-win32@hpatl20.cern.ch>
References: <19980924230003 DOT 29372 DOT qmail AT findmail DOT com>
Reply-To: "Lassi A. Tuura" <lat AT iki DOT fi>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: Steve Bennett <sbennett AT ichips DOT intel DOT com>
Cc: gnu-win32 AT cygnus DOT com

|> The same executable, however, will not run when copied onto a
|> Transarc mounted AFS drive. Bash complains that there is "no such
|> file or directory". The permissions (when I do an ls -l) give owner,
|> group and global execute and read permissions. 
|> 
|> I get the same results when I build on the AFS drive. The build seems
|> to go fine (just as it does on the NFS drive), so I am at a loss
|> here. 
|> 
|> Any ideas?

Revert back to AFS 3.4a/Patch 3 (or 5).  Patch 9 might also work, I have
not yet tried it, but none of the patches above five work.  This has
been so at least for us on NT 4.0 SP3.

BTW, at least patch 3 will fill your event log in approximately three
minutes when you build on AFS (i.e. if run make with lots of files).  It
will create a event notification some five times a second.  And it will
be *really* slow, something like a factor of 20 slower than on local
disk.  I don't know if these two things are related.

Hope this helps,
//lat
--
With sufficient thrust, pigs fly just fine.  However, this is not
necessarily a good idea.  It is hard to be sure where they are going
to land, and it could be dangerous sitting under them as they fly
overhead.  --RFC1925, "The Twelve Networking Truths"

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".