Hello,
Jeremy Allison wrote:
Precisely. This is something that isn't new and has been in Samba
a long time. I don't think it's a critical bug that needs urgent
code changes - unlike the ACL issues which were bugs in new
functionality.
Alright, so there is a design issue in samba that has been
On Thu, 21 Apr 2005 09:24:45 +0200 Peter Kruse [EMAIL PROTECTED] wrote:
Alright, so there is a design issue in samba that has been there
for a long time, and as there a solutions (EAs) no need to
do anything about it. Fine, go ahead and mark the bug as
wontfix. But please also put somewhere
Hello,
Jeremy Allison wrote:
It should still be fixed if you do attrib -r filename
before copying to the file however...
That doesn't work, which is a problem as well, unless you also have
dos filemode = yes.
Peter
--
To unsubscribe from this list go to the following URL and read the
Doug VanLeuven wrote:
I don't know if it's by design or not.
Looks to me that the read only flag in windows is triggered by the write
bit on the primary owner.
yes, that's what I think, too.
IMHO use delete readonly = yes to get the unix semantics.
Refer my previous post on this
Hello,
Schaefer Jr, Thomas R. wrote:
I've been messing with it some more. Yeah, you can take ACL's out of
the picture. It basically boils down to in UNIX, even if the owner of
the file does not have write access, if the group does have write access
and you are a member of the group you can write
On Tue, 19 Apr 2005 20:44:24 -0500
Jeremy Allison [EMAIL PROTECTED] wrote:
This is actually a separate (non-ACL) issue. It's not a bug in
the ACL code. I reproduced it last night and am preparing a
response - the problem is the DOS attributes code sees it as
read-only. Do a attrib filename
On Wed, Apr 20, 2005 at 10:47:11AM -0500, Tom Schaefer wrote:
As for the read only attribute on a file, I think if the user group
combination on who's behalf Samba is acting would have the ability to
write to the file where they sitting at a UNIX shell then the read only
flag should not be
Hello,
I've kind of been hanging with Peter on this whole issue so didn't want to
just abandon him when Jeremy issued the Solaris patch that fixed things
for me.
I went and took a hard look at bug report 2619 that Peter filed and tried
to duplicate it. He is doing ACLs on specific files, not
Hello,
thanks, I just added a comment to
https://bugzilla.samba.org/show_bug.cgi?id=2619 that shows my recent
findings. It looks like not directly related to ACLs, but more
with store dos attributes. I still have the feeling that the
behaviour of samba is somewhat not what you'd expect.
I've been messing with it some more. Yeah, you can take ACL's out of
the picture. It basically boils down to in UNIX, even if the owner of
the file does not have write access, if the group does have write access
and you are a member of the group you can write to the file.
With Samba, at least
Schaefer Jr, Thomas R. wrote:
I've been messing with it some more. Yeah, you can take ACL's out of
the picture. It basically boils down to in UNIX, even if the owner of
the file does not have write access, if the group does have write access
and you are a member of the group you can write to the
On Tue, Apr 19, 2005 at 12:02:12PM -0500, Tom Schaefer wrote:
Hello,
I've kind of been hanging with Peter on this whole issue so didn't want to
just abandon him when Jeremy issued the Solaris patch that fixed things
for me.
I went and took a hard look at bug report 2619 that Peter filed
On Tue, Apr 19, 2005 at 07:09:05PM +0200, Peter Kruse wrote:
Hello,
thanks, I just added a comment to
https://bugzilla.samba.org/show_bug.cgi?id=2619 that shows my recent
findings. It looks like not directly related to ACLs, but more
with store dos attributes. I still have the feeling
Hello,
just filed it as #2619. If you wish, put additional information there.
Regards,
Peter
Tom Schaefer wrote:
Sparc Solaris / UFS file system. I have some ACL's set up for a handful
of users and its all worked flawlessly with every incarnation of Samba
I've used over the past couple
I've the same problem with AIX 4.3.3 and samba 3.0.13 (bug report #2606)
users can create and write, but cannot delete and rename
I'll try 3.0.14a but I don't think this would resolve anything
--
To unsubscribe from this list go to the following URL and read the
instructions:
Solaris guy here.
Since my last posting I HAVE managed to replicate this problem with
3.0.14a on Linux. Red Hat Enterprise Advanced Server version 3 to be
exact.
Although I did not specify --with-acl-support as a configure option.
I have never needed to compile --with-acl-support in order to
On Fri, Apr 15, 2005 at 04:43:34PM -0500, Tom Schaefer wrote:
Solaris guy here.
Since my last posting I HAVE managed to replicate this problem with
3.0.14a on Linux. Red Hat Enterprise Advanced Server version 3 to be
exact.
Although I did not specify --with-acl-support as a configure
17 matches
Mail list logo
