search for: rwxrwsr

I use rsync -ii so that it logs *all* actions. Further, I don't use any delete option but use --force. This means that if there's a name collision rsync deletes files or directories. Here's an example: 0 0 *deleting rwxrwsr-x 1969/12/31-21:00:00 scm/linux/kernel/git/amit/vs-kernel.git/objects/38 0 0 *deleting rwxrwsr-x 1969/12/31-21:00:00 scm/linux/kernel/git/amit/vs-kernel.git/objects Therefore I didn't expect to find any of these directories after the sync is finished. However I get: % ls scm/linux/ke...

...=-22 Dec 19 21:40:16 daredevil kernel: smb_create: NEW_MENU_BUTTONS_2/.appications-on.gif:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA.qHLdcj failed, error=-22 Note the difference in the erroneous file names above and the actual file names listed here: [root@daredevil designs]# ls -al frank* -rwxrwsr-t 1 root dw-core 7636 Jan 24 2000 frank-fitzgerald.gif:?Q30lsldxJoudresxAaaqpcawXc:$DATA [root@daredevil NEW_MENU_BUTTONS_2]# ls -al 'appications-on.gif:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA' -rwxrwsr-t 1 root dw-core 0 Sep 28 2001 appications-on.gif:{4c...

with extend ACL how can I force directory mode = 3775 if user is not in parent-directory group list? for example ls -l rwxrwsr-t root group1 ./dir1 (parent share) is user1 is not in group1 and try to create /dir1/dir2 thre result is not corrent rwxrwxr-t user1 group1 ./dir2 if user2 is in gorup1 and try to create /dir1/dir3 the result is corrent rwxrwsr-t user2 group1 ./dir3 I also test with inherit permissions =ye...

...rce user = administrator inherit permissions = yes force create mode = 770 force directory mode = 2770 [share2] path = /data/folder valid users = @noadmins force user = administrator inherit permissions = yes force create mode = 770 force directory mode = 2770 where: /data administrator.admins rwxrwsr-x /data/folder administrator.noadmins rwxrws--- members of @admins are also members of @noadmins --setup-- if you connect from MaxOSX (smb/cifs) to share2 and create a file the file looks like /data/folder/new.txt administrator.noadmins rwxrwx--- if you connect now from MaxOSX (smb/cifs) to...

....nongnu.org/projects/tsp and we recently hit some sftp unexpected behavior: https://savannah.gnu.org/support/?105838 when using chmod sftp client command it appears that setuid / setgid bits are not handled on the server-side. that when I sftp> chmod 2775 afile I would expect afile to show: -rwxrwsr-x 1 openssh isgreat 0 2007-04-25 00:19 afile but I get: -rwxrwxr-x 1 openssh isgreat 0 2007-04-25 00:19 afile just as if I had typed: "chmod 775 afile " on server-side. As far as I understand sftp-server.c code is seems that chmod(name, a->perm & 0777); is resp...

...to 3.0.2 what I finally did. First I thought that had solved the problem, but it didn't. I just had intimidated the users too much to complain to me about their denied write access. In analogy to a hint in the Samba Howto on Access Controls I set all the directories of this share to 2775: rwxrwsr-x domuser and put the configurations directives: force create mode = 0660 force directory mode = 0770 in the share's smb.conf part. (where "domuser" is the linux group mapped to the nt group "domain users") It didn't help! Then I messed around with opportunistic loc...

Steve, Here's how I got it all working: Create the directory you want to share (you've already done this bit), change the group ownership to be www-data and then chmod the folder 2775. You should end up with a folder whose group ownership is www-data and whose permissions are rwxrwsr-x, ie the setgid bit is set to cause files to be owned by the group www-data. Here's my share options in the smb.conf file: [WWW-Data] comment = WWW-Data on %L volume = WWW-Data on %L writable = yes path = /var/www valid users = @www-data force group = www-data force crea...

I updated samba to samba-2.0.7-4 (RedHat RPM). That didn't help. I changed the file ownership to user.group from user.user. That didn't help. I changed the file permissions to -rwxrwxr-- as you had suggested, and then it worked. (QuickBooks 99 needs *both* the file permissions set as noted *and* the ownership also.) However, when everyone closes QuickBooks the QBI file is deleted, and