similar to: ACLs and file copies/permissions

Hi all, As promised, I have started a howto document on setting up Samba with NT ACL support, based on experiences in my workplace, as documentation for this seems to be on the short side at the moment. It is available at the following address: http://www.bluelightning.org/linux/samba_acl_howto I have yet to convert it to proper DocBook format, and it needs more material (probably

Sorry - I should have addressed this to Paul Eggleston who started this thread. Regardless who started it (the Samba + ACL howto), my offer still stands if I can be of any help. I'd be happy to help with this documentation, input, proof reading, whatever. There's definately a big lack here and the Samba team already has their hands full. Rick Segeberg rick.segeberg@waterford.org

I'm looking for info on using posix acls in samba. I'd like them to look and feel like nt acls. I'd like to use the windows client to set the acls on the samba server. I've got the official samba 3 howto book, but can't seem to figure things out from there. specifically, in the past I've used a force group entry in combined with create modes to keep shared files access to

Hi everyone. I have to task where i have to replace windows NT server by samba. The problem i facing is with permissions. In windows NT , administrator can provide a share permissision like , full control, read & write but no delete and read. But i have provide same functionality in samba server. How can i set such permission , write but no delete in linux through samba. I have googled

Hello everybody, Is it possible to use ACL with Samba 2.0.7 ? Thanks

I've gotten samba working with ACLs over an XFS filesystem. Everything works pretty well with knowledge of the workarounds (cannot remove group everyone, etc.) The only major problem I have is that ACLs don't inherit correctly. The default in Windows 2000 is to have a sub folder inherit the permissions of the folder it is in on creation. By default, the Samba share's folders don't

Hi, I have a active directory domain of windows 2000. inside AD i have three user groups. Teachers, students and administration. every user has his home directory created on the fly. the umask is 0022. now what i want is that apart from users accessing there home directories there should be some other folders too which they can access. like teachers would like to access the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Would it not be possible to make the archive bit map to a Posix extended ACL instead of to the execute bit? - -Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBWDuj2dxAfYNwANIRAvmnAJ4r1Q/2X7YyPKgGWbnnB3pv6WKDjwCgn+Vd 8USnnc35+uAa2GxUmejlDBc= =Bu48 -----END PGP

It might help if you view the default directory ACLs using the getfacl utility. These are what will be inherited by stuff created in the lower directories. I would ask yourself if you actually need ACLs at all. The Samba share permissions are pretty thorough and life is far easier without ACLs as you can clearly see what permissions are in use and backups are not an issue. ACLs can quickly

All, I am currently running Samba 3.0.2a on a RHEL3 server. I would like to use the extended file systems permissions through windows, but I haven't had much luck. Here is how I am set up.... My linux box is joined to my AD domain and appears to be functioning correctly. I also have winbind set up, and functioning, although I still have some tweaking to do, it is assigning user and

I'm having trouble with ACL's and wonder how many others are too. I see conflicting answers and comments about different aspects of ACL's from many prople on the list. I was wondering if ANYONE is successfully using ACL's with Samba 3.0 or above. Questions I have that I'm sure many are asking are: Was your Samba server configured as the DC? What client OS were you

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Perhaps using a MS-DFS share would be more useful in this case? This would allow three real shares: \\server\accounting \\server\personal \\server\public which would appear as \\server\users\accounting \\server\users\personal \\server\users\public. See http://samba.org/~jht/HOWTO/Samba-HOWTO-Collection.pdf for more information on MS-DFS - -Tom

Running the command: wbinfo -aDOMAINNAME+Administrator%password works, in fact, all of the wbinfo commands report data as they should. However, when I try to connect to a share on the SMB server, I get the following error message in the logs: [2003/04/21 08:28:59, 0] smbd/password.c:connect_to_domain_password_server(1328) connect_to_domain_password_server: machine DWP rejected the tconX on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What is the standard procedure for making edits of smb.conf take hold? For example, what I'm seeing is a share that has given R/W access to a user named Tom, when I change Tom to read only, he is still able to write to that share until I stop Samba and restart it. The documentation seems to refer to a 1 minute reread of smb.conf, but I don't

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ~ /usr/bin/net ads join -Udennisb dennisb password: [2004/11/02 17:31:56, 0] libads/ldap.c:ads_add_machine_acct(1006) ~ Host account for if-srv-hos1 already exists - modifying old account [2004/11/02 17:31:56, 0] libads/ldap.c:ads_join_realm(1342) ~ ads_add_machine_acct: No such object ads_join_realm: No such object Also: net user | wc -l reports

I have been searching for info on this and haven't found an authoritative answer. From what I have read, oplocks are good because they increase connection speeds, but they are bad because they don't really work, but they actually do work, but they only work in some cases, etc etc. so, here's my problem and my question together: I get tons of these messages every day (over a thousand a

Hi there, I have been trying to set up Samba 2.2.8 to connect to our Windows 2000 domain, and provide shares that support file permissions as a Win2K box would, under Red Hat 8.0. To that end I recompiled the kernel (2.4.20) with patches from acl.bestbits.org, enabling ext2 and ext3 EA and ACL support. I set up winbind, joined the domain OK, and got name resolution working pretty well. Everything

Mandrake 9.1's kernel needs a patch to support ACL's : http://qa.mandrakesoft.com/show_bug.cgi?id=3615 Regards, Gana?l LAPLANCHE. bgmilne@cae.co.za@lists.samba.org on 07/23/2003 06:09:59 PM Envoy? par : samba-bounces+ganael.laplanche=edf.fr@lists.samba.org Pour : samba@lists.samba.org cc : Objet : Re: [Samba] Unofficial Samba+ACL HOWTO -----BEGIN PGP SIGNED MESSAGE-----

This is probably a hot topic, and if this has been beaten to the ground, forgive me. I'm not a regular part of the Samba community. Although I have been using Samba for years, I now have to use it in a corporate environment utilizing some of it's more modern features. Let me just say, that it's been several hours of testing/troubleshooting to get where I am now. (And I don't

Samba doesn't allow connections from usernames that have & in them. For example, using 2.2.5 and winbind with security = DOMAIN password server = win2kmixed workgroup = MIXEDDOMAIN all my users can login, (for example MIXEDDOMAIN+aho, MIXEDDOMAIN+tdickson), but my users named "&" and "bobalso&" (which should be MIXEDDOMAIN+& and MIXEDDOMAIN+bobalso&)