greg (AT) fqdn (DOT) com wrote:
Hi,
a windows client if I attempt to modify the permissions on a file which
resides on a linux server, when I hit "apply or ok" my changes are lost.
Doing it from the unix cli (using setfacl) works as expected and the
changes are not lost.
Yet on windows if I right click - properties - Security. select add, add
a user or group, hit Apply and the user/group I just added is removed.
ACL support is properly configured as far as I am aware on the linux file
server.
any one with any idea as to what I should look at, that would be great,
thanks!
It has been a bummer modifying all the permission change requests by hand.
What version of kernel are you using?
There is a patch to 2.4.x kernel tree here:
;a=commitdiff;;
This could be the problem.
James Kosin

Its actualy a 2.6 kernel James, but thanks for the quick reply.

Have a great day,
greg

Linux exec 2.6.5-7.191-default #1 Tue Jun 28 14:58:56 UTC 2005 i686 i686
i386 GNU/Linux

greg (AT) fqdn (DOT) com wrote:
>Hi,
>>
>a windows client if I attempt to modify the permissions on a file
>which
>resides on a linux server, when I hit "apply or ok" my changes are
>lost.
>>
>Doing it from the unix cli (using setfacl) works as expected and the
>changes are not lost.
>>
>Yet on windows if I right click - properties - Security. select add,
>add
>a user or group, hit Apply and the user/group I just added is removed.
>>
>ACL support is properly configured as far as I am aware on the linux
>file
>server.
>>
>any one with any idea as to what I should look at, that would be
>great,
>thanks!
>>
>It has been a bummer modifying all the permission change requests by
>hand.
>
What version of kernel are you using?

There is a patch to 2.4.x kernel tree here:
;a=commitdiff;;

This could be the problem.

James Kosin
--

greg (AT) fqdn (DOT) com wrote:
Its actualy a 2.6 kernel James, but thanks for the quick reply.

Have a great day,
greg

Linux exec 2.6.5-7.191-default #1 Tue Jun 28 14:58:56 UTC 2005 i686 i686
i386 GNU/Linux

Greg,

The same patch applies to the 2.6.x kernel tree.

;a=commitdiff;;

James Kosin

thanks again James!

I'm downloading the 2.6.15-git12 source/patch and will give it a go as the
changelog shows this patch was rolled in.

Not being a developer, this may be a stupid question and I woudln't know
it , can I take proc.c from the page you supplied, replace the existing
one in, and recompile my 2.6.5-7.191 kernel from source? I guess what
i'm asking is if it is version sensitive. I ask as this is a sles9 box
under support; I'd rather try and keep things as much the way it was
shipped as possible.

thanks james for your help,
greg

--
greg (AT) fqdn (DOT) com wrote:
>Its actualy a 2.6 kernel James, but thanks for the quick reply.
>>
>Have a great day,
>greg
>>
>Linux exec 2.6.5-7.191-default #1 Tue Jun 28 14:58:56 UTC 2005 i686 i686
>i386 GNU/Linux
>>
>
>
Greg,

The same patch applies to the 2.6.x kernel tree.

;a=commitdiff;;

James Kosin

greg (AT) fqdn (DOT) com wrote:
thanks again James!

I'm downloading the 2.6.15-git12 source/patch and will give it a go as the
changelog shows this patch was rolled in.

Not being a developer, this may be a stupid question and I woudln't know
it , can I take proc.c from the page you supplied, replace the existing
one in, and recompile my 2.6.5-7.191 kernel from source? I guess what
i'm asking is if it is version sensitive. I ask as this is a sles9 box
under support; I'd rather try and keep things as much the way it was
shipped as possible.

thanks james for your help,
greg

Greg,

It appears the patch is across all versions. You should be able to
patch your current kernel, if you have the source.

I'm also not sure if this is the exact problem. I build my own kernel
from the 2.4.x source tree frequently and update my RPMs by hand, so I
try to keep track of the patches. This one sticks out; because it
involves the smb file sharing and possible corruption with the file
permissions.

Good Luck,
James Kosin

In your smb.conf write:

inherit acls
map acl inherit

You need a extended attributed filesystem.

2006/1/16, James Kosin <jkosin (AT) intcomgrp (DOT) com>:
>
>
>
greg (AT) fqdn (DOT) com wrote:
thanks again James!

I'm downloading the 2.6.15-git12 source/patch and will give it a go as
the
changelog shows this patch was rolled in.

Not being a developer, this may be a stupid question and I woudln't
know
it , can I take proc.c from the page you supplied, replace the
existing
one in, and recompile my 2.6.5-7.191 kernel from source? I guess what
i'm asking is if it is version sensitive. I ask as this is a sles9 box
under support; I'd rather try and keep things as much the way it was
shipped as possible.

thanks james for your help,
greg
--
Greg,

It appears the patch is across all versions. You should be able to
patch your current kernel, if you have the source.

I'm also not sure if this is the exact problem. I build my own kernel
from the 2.4.x source tree frequently and update my RPMs by hand, so I
try to keep track of the patches. This one sticks out; because it
involves the smb file sharing and possible corruption with the file
permissions.

Good Luck,
James Kosin