I'm trying to get my linux smb/cifs client recognize the executable bits that are set on some files on a share on a linux smb server.

Here is our setup:

  1. Linux server exporting some directories via smb to clients
  2. Many windows clients accessing the shared directories
  3. Some linux clients accessing the shares

We've got some shell scripts on the shares that have the executable permission bit set on the linux server. We ssh into it and can execute them without problems.

Thanks to samba's map options, we can export the unix executable bits as archive, system and hidden permissions via the smb protocol, which works.

Now to close the loop, I need to find a way to map those archive, system and hidden bits back to the ugo executable bits on my linux clients. I didn't find a setting for that in the mount.cifs man page, but maybe it's possible somehow else?


Simply switching to NFS is something I'd like to avoid, because we have many window clients that also use the shares. Administrating NFS would be additional work.

link|improve this question

75% accept rate
I know it doesn't answer the question, but why not offer NFS for the Linux clients? Far easier than dealing with the fiddly Samba options and easier to administer. – Adrian Jan 16 at 19:45
Not being snarky, but you're putting in more work fiddling with Samba than I ever did with NFS. NFS is pretty much fire & forget unless you're using NFS4, and then it's slightly more involved. And I've always found that it's easier to automate and centrally manage NFS settings than it is to automate Samba. – Adrian Jan 16 at 21:38
feedback

1 Answer

Why don't you just create two different configuration sections in smb.conf? One for the Windows clieants as it already is, and one for the linux clients that omits the map x = yes lines.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.