ASU over NFS cannot execute files because of mandatory locking

[Bo Forsberg]

ASU creates files with mode -rw-rwSr-- by default. To NFS, the "S" mode means that the file uses mandatory locking, which NFS does not support, so NFS returns "access denied" when the Windows user tries to execute the file.
Does anyone have a suggestion how to deal with this? I hoped to somehow make ASU create files with some other permissions, but I haven't found any registry key to accomplish this. Seems to be nothing to adjust in NFS either. I run a script which does chmod g+s to all the files regularly, but I cannot run this often enough to eliminate all problems.
HELP!
(yes, we'll convert to CIFS eventually, but we can??t do that just now).

[Michael Steele_2]

I don't know nor would I recommend it since mandatory locking is your update safety which prevents data corruption from occurring when more than one user grabs a file and attempts to write to it. This way only one user can update at a time.

That's why its there.

[Bo Forsberg]

The files in question are accessed only via a single ASU server, and not via Unix. I interpret the ASU Admin Guide to mean that letting Unix handle locking is only needed if more than one ASU server will access the files. That would meen that ASU itself keeps track of files locked by Windows clients. I may be wrong, of course... 8-)

[Don McCall_1 · Accepted solution]

This is controlled by the registry parameter
SYSTEM/CurrentControlSet/Services/AdvancedServer/FileServiceParameters UnixFilePerms

On older revisions this defaulted to 02664 (octal).
Current asu versions default this to 0664.
You can change this using regconfig -s SYSTEM/CurrentControlSet/Services/AdvancedServer/FileServiceParameters UnixFilePerms REG_DWORD 0664
You will have to restart asu to make this change take effect.

[Bo Forsberg]

Many thanks, that solved the problem!
I kinda got stuck on fiddling about with "Use_unix_locks" and the like...
/Cheers,
Bo