From: "Mark Sweitzer" <ms2k@email.com>
To: "Linux-Admin (E-mail)" <linux-admin@vger.kernel.org>
Subject: Samba and permissions
Date: Thu, 1 Aug 2002 23:38:59 -0600 [thread overview]
Message-ID: <000c01c239e7$5a34e600$e5d096d8@w2kpro> (raw)
I have a Redhat 7.3 system running Samba server for Windows98 networked
users. These users are registered users on the Linux box, using encrypted
passwords mirrored in Samba's password list. These users need to have file
ownership for existing and new files edited on their Windows PC's. To allow
this, I've made the following mods:
in etc/profile: umask 002
in each user's data directory: chmod -r 7775
in "etc/samba/smb.conf" global settings section:
create mask = 7775
inherit permissions=no
force create mode 0664
This allows proper file ownership, and I then set all files in each user's
directory to be "read only" to all users but its owner. It also allows me to
assign other group permissions as is necessary without disrupting the
ownerships. Sometimes though, a user will copy a data file from their own
directory into another user's directory, with the intention of having the
file be "writable" by the 2nd user. However, the file continues to hold the
original ownership, and is "read only" to the 2nd user, even though it now
resides in the 2nd user's data directory.
I need to find the correct "chmod" command, or other method, to allow these
special files to become writable. It needs to be via a one-time command or
script entered at the server, as these Windows users do not have access to a
Linux shell, only to their Samba network shares.
I've also tried "inherit permissions=yes" but it did not correct the
problem.
Any suggestions?
***********************
Thanks,
Mark S.
reply other threads:[~2002-08-02 5:38 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='000c01c239e7$5a34e600$e5d096d8@w2kpro' \
--to=ms2k@email.com \
--cc=linux-admin@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).