Sounds like you want revision control...because you cant do that at the /etc/exports level...the netapp doesn't care WHO has it open when, just that they can or cant.

On 4/18/05 12:55 PM, "Doug Chomyn" chomyn@corefa.com wrote:

Um, I'm looking at dynamic sharing, where if host 1 has rw, hosts 2, 3, 4 have r only. when host 1 relinquishes w, the hosts 2, 3, 4 have the possibility of opening the file for w since they too have the privilege.

McCarthy, Tim wrote:

...

Why not: (6.5.1 or higher) exportfs -p ro=host1:host2:host3,rw=host4:netgroup1:subnet/24 /vol/vol1/path

--tmac

-----Original Message----- From: Doug Chomyn [mailto:chomyn@corefa.com] Sent: Monday, April 18, 2005 2:24 PM To: toasters@mathworks.com Subject: Re: File Sharing Windows <> NFS Volume on R150 (6.5.2R1) ...

Yes, we have SFU installed on the Windows clients and can easily access the NFS volumes, but I need the "file share" as if the shared document was on a Windows NT volume, permissions-wise that is ...

emilio brambilla wrote:

...

hello,

Doug Chomyn wrote:

...

document R only, etc, etc. Ordinarily we would do a re-share via Samba, or perhaps make a CIFS volume share, but I'm trying to reduce complexity (and we're not going to buy a CIFS license) ... anyone have experience

if you have only a few workstations accesing the storage with windows sharing you can try installing on each workstation the "microsoft nfs client" you can download from http://www.microsoft.com/windows/sfu/

we did use this workaround 6 month ago to allow a few windows box to access a nfs-only fas270C (the customer has 300 unix boxes and only 2 windows clients so he did not agree to buy the cifs license)

it's still working and the customer is habby about it, but we had to force the workstation to use nfs over tcp in order to have a stable connection

if you need it, this is the registry key you have to set to force tcp connection: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Client for NFS\CurrentVersion\Default] "PreferTCP"=dword:00000001