Executable problems on afp shares

[gw1500se]

This is driving me absoiutely insane. Please, will someone save me from the asylum?

I have an afp share (OD workgroup managed) that is mounted for multiple users. On that share is an executable (an app but not a package). The permissions on it are -rw-r–r– (which makes no sense from a Unix perspecitve) but finder info shows it as an application and it works for some. That is the problem, it works for some users but not others. In the cases where it does not work the permissions are the same however finder info shows it as a classic application (which of course it is not). I have to assume there is something in the file header that tells OS X it is executable (even though Unix thinks it is not) and provides the icon. So why do not all users see the same thing but instead see a classic application and display the generic application icon? More importantly, how do I get all users to see it the correct way so they can use it? TIA.

[superrcat]

If it is a Mach-O application the executable permission bit has to be set in order for it to work. Classic applications (CFM applications) are not UNIX executables and ignore the executable permission bit. Both Carbon (Mach-O) and CFM applications have a ‘cfrg’ resource, but Carbon applications have a ‘carb’ resource to let Mac OS X know if the application can run natively.

So since this is a Carbon application and depending on who you want to access it, can you set the permissions on the application to 755?

[gw1500se]

Thanks but no joy. It still shows as a Classic Application. Another discovery is that it shows up corrrectly and works (even with 644) for the user that copied it onto the share. Even after a ‘chown admin’ is done.

[gw1500se]

Nevermind. This is apparently a problem with the application itself. There is some incompatability with afp from a 10.4 server. If I serve it out as an smb share, it works.

[Author]

Posts