[Samba] Re: chown failure on a samba share

Shirish Pargaonkar shirishpargaonkar at gmail.com
Wed Mar 11 14:50:54 GMT 2009


On Wed, Mar 11, 2009 at 6:13 AM, Volker Lendecke
<Volker.Lendecke at sernet.de> wrote:
> On Wed, Mar 11, 2009 at 05:28:00AM -0500, Shirish Pargaonkar wrote:
>> >> smb: \> chown 65534 file2
>> >> chown uid gid file
>> >>
>> >> smb: \> chown 65534 65533 file2
>> >> NT_STATUS_ACCESS_DENIED chown file \file2 uid=65534, gid=65533
>> >>
>> >> With just uid supplied to chown command, I do not get any error but
>> >> nothing changes on the server.
>> >>
>> >> cifstest8:/tmp/cifstest8 # cat /etc/passwd | grep nobody
>> >> nobody:x:65534:65533:nobody:/var/lib/nobody:/bin/bash
>> >>
>> >> cifstest8:/tmp/cifstest8 # cat /etc/group | grep nobody
>> >> nobody:x:65533:
>> >> nogroup:x:65534:nobody
>> >>
>> >
>> > chown("file2", 65534, 4294967295) = -1 EPERM (Operation not permitted)
>> >
>> > That gid of 4294967295 does not look right
>> >
>>
>>
>> ret = SMB_VFS_CHOWN(conn, fname, set_owner, (gid_t)-1);
>>
>> is failing.
>
> "man 2 chown" gives:
>
> If the owner or group is specified as -1, then that ID is not changed.
>
> This sounds like either a 32/64 bit problem or a problem
> with SELinux.
>
> Volker
>

Volker,

yes, I think problem with SELinux.

With this samba server, no such problem

smbd -V
Version 3.0.22-3-SUSE-CODE10

Thanks for the help.


More information about the samba mailing list