From: Craig Allison <craig@(email surpressed)>
Subject: NFS Permissions & Snow Leopard
   Date: Wed, 02 Sep 2009 12:17:28 -0400

Craig Allison wrote:
> Just to let everyone know I've just done an install of Rush version
> 102.42a9 on Snow Leopard and all works well as long as you install Rosetta.

	Actually, no, you /shouldn't/ need Rosetta
	if you comment out this section of the install script:

# rez=$RUSH_DIR/etc/bin/Rez
# for i in $RUSH_DIR/examples/bin/input.app/Contents/MacOS/input \
#        $RUSH_DIR/examples/bin/input; do
#     echo -n "--  Creating resource forks for 'input': "
#     i_dir=`dirname $i`
#     if ( cd $i_dir && $rez -t APPL $RUSH_DIR/etc/bin/mac.r -o input ); then
#         echo OK
#     else
#         echo "FAILED while working on ${i}"
#       let errors++
#     fi
# done

	The rush binaries will all run fine (including the GUIs)
	without the above 'Rez' code. This is only needed for
	older versions of OSX that depended on resource/data forks.

	Next release will have a fix for that, but you can just comment
	out the section by hand.

	If you're installing rush Universal build (which has the intel
	and ppc binaries) you won't need Rosetta. Rosetta would only
	be needed if you had an old version of Rush that was PPC only,
	which would be about 3 years old or more.

> Slightly off topic as far as rush is concerned, but I wondered if anyone
> out there is using Leopard or Snow Leopard over NFS to an XSan share and
> is getting the same issue as me with permissions.
> 
> If I open a tif file from a Leopard box client, for example, edit it
> then try to save over the file I get a "file locked" permission error,
> this is using both Preview and Photoshop.

	What are your NFS mount flags?
	Also, while the file is open, does ls(1) show any interesting
	flags on the file? (eg. 'ls -la@" (extended attributes), 'ls -lae' (ACLS) )

	I often disable file locking over NFS because I've never trusted it;
	see 'man mount_nfs' the 'nolocks' option.

	Not sure though if this will affect your situation or not.

	It sounds like somehow the lock is remaining active.

	I'll try your test with Preview in just a bit.
	Could be an actual problem with how

> And just another gripe with Snow/Leopard, why does the Finder often show
> a bunch of identical 2k dpx files as different file sizes, even though
> Get Info shows the correct, and identical, byte count???? i.e. A byte
> count of 12,754,744 displays in the Finder as 15.4Mb, with the next file
> in the sequence showing as 17.3Mb even though it has the same byte count!!

	Wow,  sounds like a Finder bug.

	IIRC, in Snow Leopard the Finder is a complete rewrite,
	so there could easily be hiccups in this new code. For a long time
	back in the 10.0/10.1 days, there were bad bugs in the Finder's
	computation of disk size.

	Snow Leopard is only 10.5.0 at the moment (".0" releases are always
	the most unstable) -- there will probably be updates that fix it.
	But you might want to report it, giving details of your Xsan/NFS
	mount flags and file system details (HFS, HFS+).

	I'll try a few experiments later today with some large files
	just to check this, as I'm curious.


-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

Greg Ercolano wrote:
> Craig Allison wrote:
>> Just to let everyone know I've just done an install of Rush version
>> 102.42a9 on Snow Leopard and all works well as long as you install Rosetta.
> 
> 	Actually, no, you /shouldn't/ need Rosetta
> 	if you comment out this section of the install script:
> [snip]
> 
> 	The rush binaries will all run fine (including the GUIs)
> 	without the above 'Rez' code. This is only needed for
> 	older versions of OSX that depended on resource/data forks.

   Actually, I stand corrected on that.

   During testing last week, I noticed that all the Mac Universal
   releases of Rush to date (102.42a9b and older) had one binary
   that was *still* PPC that I didn't know about; the little executable
   that is in all the submit-*.app dirs.

   To address that, I've posted a patch in this newsgroup article:
   http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1885

   So that will fix the problem with the existing versions of Rush
   for OSX.

   There will also be a maintenance release of Rush (102.42a9c) that
   will beta next week that has a fix for that, as well as fixed for
   other obscure issues that came up over the last month or two.