I can understand that.
However, I'm a bit confused about how this is supposed to be practical
in the case of Samba. Samba runs as root, so it can see everything.
I'm telling it to share a particular folder. Why should it look at the
ACLs of folders above that, when there's no way they will
No, you can use /home/srv/share as long as srv (under home) is 755
permissions. Samba does run as root, but it also still obeys the rules
underlying file system.
Ricky
On Thu, Aug 22, 2013 at 10:19 AM, Kevin Field k...@brantaero.com wrote:
I can understand that.
However, I'm a bit confused
Oh, so it only looks at the immediate parent's permissions? Not the
grandparent? I find that even more bewildering but a whole lot easier
to work with if that's the case :)
Thanks,
Kev
On 2013-08-22 11:44 AM, Ricky Nance wrote:
No, you can use /home/srv/share as long as srv (under home) is
It looks at all of them, but the important thing is that its 0755 all the
way to the folder being used (if there is any XXX0 permissions on the way
to the folder it will cause things to fail, which is the case with the 'me'
part of /home/me/share as it has 0700 permissions).
On Thu, Aug 22, 2013
Oh, I see. At first I read it as /home/me/srv. Gotcha. It works!
Thanks very much Ricky! -K
On 2013-08-22 12:49 PM, Ricky Nance wrote:
It looks at all of them, but the important thing is that its 0755 all
the way to the folder being used (if there is any XXX0 permissions on
the way to the
No problem, glad its working :)
Ricky
On Thu, Aug 22, 2013 at 11:59 AM, Kevin Field k...@brantaero.com wrote:
Oh, I see. At first I read it as /home/me/srv. Gotcha. It works! Thanks
very much Ricky! -K
On 2013-08-22 12:49 PM, Ricky Nance wrote:
It looks at all of them, but the
Hi Ricky,
I don't think I should have to reboot. setenforce is documented to work
without rebooting. If I need to reboot a Linux server to troubleshoot
something like this--and I hear SELinux is often a first thing to try
disabling to troubleshoot--then it's worse than Windows for rebooting
Aha! Moving it worked. I can now see it from Windows. If I chmod 777
on the directory I can also add files to it from Windows.
However, I don't quite understand why the parent of the share directory
affects it. BTW /home/me has 700 permissions and /srv has 755. If the
+x on /srv allows
Permissions are hard to explain (possibly because I don't fully understand
them myself I guess), but if you have a directory (say /srv) and you give
it 0700 permissions, then only the person that owns that directory is able
to see anything under it, however if you give it 0755, then ANYONE can see
On Tue, 2013-08-20 at 10:22 -0500, Ricky Nance wrote:
Permissions are hard to explain (possibly because I don't fully understand
them myself I guess), but if you have a directory (say /srv) and you give
it 0700 permissions, then only the person that owns that directory is able
to see anything
Have a look at
http://www.centos.org/docs/5/html/5.2/Deployment_Guide/sec-sel-enable-disable.html
and
you will probably have to reboot after making the changes. I have seen this
cause more problems then not, so I would start with disabling it and see if
it fixes your problem. Also since you are
Temporarily turn off selinux, if that fixes your issue you will need to
adjust the selinux rules to take care of the problem (or just completely
disable selinux). Also if you do a ls -alhDZ /home/me/mytestshare before
you turn it off it can tell you if selinux is on, then run that again after
its
Interestingly, I couldn't turn off selinux using their method:
$ sudo echo 0 /selinux/enforce
-bash: /selinux/enforce: Permission denied
Perhaps it's a CentOS thing. Anyway, `sudo setenforce 0` seemed to work
in that it didn't give me an error message, but OTOH didn't seem to work
in that
On Mon, Mar 10, 2008 at 4:44 PM, João Amâncio Ferreira
[EMAIL PROTECTED] wrote:
Hello all,
I have a SAMBA share called share_a and it is working fine (below is a
snapshot of it):
[share_a]
path = /shares/share_a
browseable = no
valid users = @group_a @group_b @group_c
write list =
João Amâncio Ferreira wrote:
Hello all,
I have a SAMBA share called share_a and it is working fine (below is
a snapshot of it):
[share_a]
path = /shares/share_a
browseable = no
valid users = @group_a @group_b @group_c
write list = @group_a @group_b
read list = @group_c
create mode = 777
I do agree with you, this really don't make any sense, but this kind of
police used to work in an old windows NT machine and the permissions was
just like that.
I don't really know if there is a way to make it work with posix acls,
or samba...
If anyone has any ideia...
Sorry the poor english.
Donald W Watson wrote:
If I have a samba server with the following share:
[share1]
readlist= user1
path = /tmp/share1
writelist = user2
On the surface this indicates that user1 can only read files in the share,
while user2 and read and write.
Message-
From: rruegner [mailto:[EMAIL PROTECTED]
Sent: 29 October 2003 5:13:pm
To: Tom Czachor; [EMAIL PROTECTED]
Subject: Re: [Samba] share permissions
hi , please post more of your setup smb.conf samba version etc
to get qualified answers
Best Regards
- Original Message -
From: Tom
hi , please post more of your setup smb.conf samba version etc
to get qualified answers
Best Regards
- Original Message -
From: Tom Czachor [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 29, 2003 5:37 PM
Subject: [Samba] share permissions
I am trying to setup Samba in
How can I add another user or group to Samba so the teacher and student
have full
control over the folder?
Have something like
valid users = user1 user2 -- should be self explanatory
write list = @teachers --this is the groupings (same as *nix Groups)
something likt that
Cheers,
20 matches
Mail list logo
