All of lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Yeager <casey-AWiv9L5iBJJF6kxbq+BtvQ@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Creating new files on CIFS mount ignores fmask/file_mode
Date: Thu, 05 Jul 2012 20:18:32 -0500	[thread overview]
Message-ID: <4FF63CE8.3040403@yeagerweb.com> (raw)

After switching from smbfs mount, the dmask/dir_mode and fmask/file_mode 
no longer have an effect on the newly created files. It seems to use the 
system umask instead. Is there a way to have cifs mount create files 
with permissions like smbfs does?

--------- smbfs mount showing new file permissions ---------

root@osiris:~# cat /etc/fstab | grep smbfs
//192.168.1.23/YEAGER /mnt smbfs 
gid=users,fmask=0660,dmask=0770,username=xxxx,password=xxxx 0 0

root@osiris:~# mount /mnt ; cd /mnt/test

root@osiris:/mnt/test# touch test_smbfs ; ls -l test_smbfs
-rw-rw---- 1 root users 0 2012-07-05 18:45 test_smbfs

--------- cifs mount showing new file permissions ---------
(note: substituting fmask for file_mode and dmask for dir_mod has had no 
effect on outcome)

root@osiris:/# cat /etc/fstab | grep cifs
//192.168.1.23/YEAGER /mnt cifs 
gid=users,file_mode=0660,dir_mod=0770,username=xxxx,password=xxxx 0 0

root@osiris:/# mount /mnt ; cd /mnt/test

root@osiris:/mnt/test# touch test_cifs ; ls -l test_cifs
-rw-r--r-- 1 root users 0 2012-07-05 18:47 test_cifs

--------- re-mounting changes to correct permissions ---------

root@osiris:/mnt/test# cd / ; umount /mnt
root@osiris:/# mount /mnt ; cd /mnt/test

root@osiris:/mnt/test# ls -l test_cifs
-rw-rw---- 1 root users 0 2012-07-05 18:47 test_cifs


testing platforms:
RHEL 4 with samba 3.0.33
Slackware 12.1 with samba 3.0.37

                 reply	other threads:[~2012-07-06  1:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FF63CE8.3040403@yeagerweb.com \
    --to=casey-awiv9l5ibjjf6kxbq+btvq@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.