On Fri, 17 Jun 2011 10:32:44 +0100 David Aldrich <David.Aldrich@xxxxxxxxxxxx> wrote: > Hi > > We are building a Linux app under Centos 5.3, using gnu make 3.81 and gcc 4.12. The working directory is on a remote machine and is either a Samba share or a Windows 7 share. We find that in the case of a Windows 7 share the resulting executable has the sticky bit set in group: > > On Windows 7 share: > > -rwxrwSrwx 1 <snip> myapp > > On Samba share: > > -rwxrwx--x+ 1 <snip> myapp > > The Sticky bit prevents another user in the group from executing the application. > > Please will someone suggest how we can prevent the sticky bit from being set? > > I found a reference on this list that may be relevant: > > http://lists.samba.org/archive/linux-cifs-client/2007-October/002294.html > > Is this a problem with the CIFS client? > > Best regards > That's actually not the sticky bit, but rather the sgid bit. The capital S means that it doesn't have the group execute bit set, which has a special meaning to the kernel -- it tells it to enforce mandatory locking. You probably want to use the file_mode/dir_mode mount options here. -- Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
