I've found one tricky hint to use SAMBA server in AFS environment.
Here I want to propose that SAMBA server should change its default umask
when it creates files.
As far as I know, SAMBA client can't set mode bits of files
it creates via SAMBA server, especially from PC. (It it can, I'm wrong.
Please let me know.) The default modebits of SAMBA seems 0755.
Generally, the 0755 mode bits does not produce problems. However,
when we share files in one directory by using AFS ACLs, this can be a big
problem because SAMBA server checks the ownership and mode bits of files
before it transfers the file commands to AFS Cache manager.
Let's see the following example, there's a directory 'A' which
has write ACLs to 3 users. And the 3 users want to share files in the
directory. (They should write and modify files which were made by other
users.)
ACL of directory A;
Access list for A is
Normal rights:
userA rlidwka
userB rlidwk
userC rlidwk
Let's check out the following scenario;
1) userA creates file 'fileA' via SAMBA server
2) fileA has the ownership and mode bits like this;
6 -rw-r--r-- 1 userA staff 3032 Feb 12 13:33 fileA
3) when userB or userC wants to write or modify 'fileA',
their operation is rejected by SAMBA server because fileA
is not owned by A nor B and the file has 644 mode bits.
4) However, since AFS ACLs are properly set, userB or userC
CAN write 'fileA' if SAMBA server transfers their command
to Cache manager.
The solution of this problem is to change default UMASK
of SAMBA server when it creates files, to 000. Or SAMBA server should
not check the ownership and mode bits when it is compiled for AFS.
--
___________________________________________________________________________
_____ ___ __ __
__/\__ |_ _| / _ \ \ \_/ / Remember Yesterday, Dream about Tomorrow
\ / | | | /_\ | \ / but ... LIVE TODAY !!!
/_ _\ | | | _ | | |
\/ __| | | | | | | | [EMAIL PROTECTED] (Jae-young Kim)
|___/ |_| |_| |_| Researcher, Computer Center/POSTECH, KOREA
___________________________________________________________________________
