search for: ownerhip

Displaying 4 results from an estimated 4 matches for "ownerhip".

Did you mean: ownership
2001 Oct 18
3
group ownership
...or 512 Oct 17 13:49 . drwxrwxrwt 6 sys sys 1536 Oct 17 13:49 .. -rw-r--r-- 1 rwalkup visitor 79 Mar 13 2001 hosts drwxr-xr-x 3 rwalkup visitor 512 Mar 13 2001 inet -rw-r--r-- 1 rwalkup visitor 330 Mar 21 2001 vfstab Is it not possible that the group ownerhip be changed to cdburners as the rsyncd.conf file indicates? cdburners exist on both client and server. any ideas would be greatly appreciated. Thanks, Ron
2006 May 31
3
Cannot delete files from samba share
...n upgrade from samba 2.2.8a to 3.0.22 we have been unable to delete files on a samba share using an XP client. We were previously able to delete these files when using 2.2.8a. The problem occurs when we have a particular sub-set of permissions. Directory permissions on UNIX are set to 775 and ownerhips to usera : group1. This should mean that either usera or anyone who belongs to group1 should be able to delete any file within the directory irrespective of what the file permissions and ownerships are. From UNIX this is the case. Using an XP client on samba 2.2.8a this is the case. On s...
2000 May 23
1
Samba digest 2532 / Problem with "force create mode" et. al.
Hi, Frankly spoken you have a real RTFM problem. The manual pages for smb.conf say that "create mask" and "create mode" are equal. It also says that there is only a "force XXXX mode" (where XXXX is either create or directory). So a replacement of mask with mode will do the thing. The other mistake is that there is no "force create group" parameter. The
2003 Jul 08
1
Modify ownership of a file or folder from within windows - Please help!
Hi I have posted this message twice already I really need to know if this can be done with samba and winbind. Please can anyone help? I have a Redhat 8 server running samba 2.2.8a and have configured samba to use winbind so that I can control access to the samba file shares using user and group accounts that have been set up in our windows NT domain. This all works fine on the shares I set up