https://bugzilla.novell.com/show_bug.cgi?id=437003
User danielstefanmader@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=437003#c3
Daniel Mader changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|danielstefanmader@web.de |
--- Comment #3 from Daniel Mader 2008-10-21 02:53:50 MDT ---
Sorry for the confusion: I am not reporting a defect for SLES but for a weird
client behavior.
<OT>
<rant>
Even if I would like to, I have no idea where to report such a bug: 10.1
product is discontinued, which leaves no option to report bugs. The Customer
Center is a mess of irrelevant options and suboptions and I have never been
able to find the essential information there within reasonable amount of time.
Where do I file a simple, electronic technical support question or a bug
report? What is this CID, and where can I find it? When our 3yrs subscription
runs out we will definitely have to think about finding another vendor since
this full subscription is absolutely of no use and just a waste of money.
</rant>
</OT>
For some reasons we have decided not to use ACLs but prefer to set permissions
masks like this for each of the collaboration shares:
create mask = 740
directory mask = 750
force create mode = 220
force directory mode = 770
force group = optiker
read list = @optiker
write list = @optiker
This works very much like expected on the *server file level*, i.e. ls -la as a
user on the server on such a share gives:
-rw-rw---- 1 aatz optiker 1250358 2008-10-17 15:56 someFile
drwxrwx--- 2 aatz optiker 4096 2008-10-17 16:55 someFolder
This is the expected and wanted behavior (readable and writeable for the
respective primary group.
Yet, the same command from a Linux client which has the respective shares
mounted with pam_mount gives something totally meaningless:
-rwxrwSrwx 1 mader optiker 1250358 2008-10-17 15:56 someFile
drwxrwxrwx 1 mader optiker 0 2008-10-17 16:55 someFolder
BTW: The same holds for a MacOS X client:
-rwx------ 1 jf jf 1250358 17 Okt 15:56 someFile
drwx------ 1 jf jf 16384 17 Okt 16:55 someFolder
As you can (hopefully) see, it is not even possible to check who the owner of
the file is. I am not even talking about changing the permissions but checking
should be possible. Or am I misktaken here?
So, imho, lhis looks like a smbd/smbclient/mount.cifs problem to me. I don't
know if this would be different with ACLs -- whe haven't checked.
Here's the missing information for the server (rpm -qa samba*):
samba-3.0.28-0.8
samba-winbind-3.0.28-0.8
samba-pdb-3.0.28-0.8
samba-client-3.0.28-0.8
and for the client (rpm -qa cifs*):
cifs-mount-3.2.3-0.1
Hope this helps to sort out which part of the setup is the culprit :)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.