similar to: FreeBSD 6.1 ACL support

https://bugzilla.samba.org/show_bug.cgi?id=7884 Summary: Workaround for ACL problem with ZFS under FreeBSD Product: rsync Version: 3.0.7 Platform: x64 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: trasz at

Hi people. Im reading the samba manual to join my freebsd box with to an win2k3 AD Domain, i install samba from ports with support for AD, already check that my samba program has been build with support for kerberos, ldap and all the stuff the manual recommended, now about kerberos, we have some stuff in /etc/rc.conf # # kerberos. Do not run the admin daemons on slave servers #

If you add to vfs module to a share you also have to explicit add acl_xattr , that's what i do when i want to add another module and keep acl_xattr on the same share, if i'm not doing right way someone correct me . ----- Original Message ----- From: "samba" <samba at lists.samba.org> To: "samba" <samba at lists.samba.org> Cc: "Oleg Cherkasov"

Thanks for the help on the missing '-p1' for the acl and xattr patches. Things are configuring and making properly now. However, I couldn't help noticing this during the configure: checking whether to support ACLs... ACLs requested -- running tests checking for acl_get_file in -lacl... no checking for ACL support... yes checking ACL test results... Using posix ACLs checking for

On 06. aug. 2018 16:37, Oleg Cherkasov via samba wrote: > On 06. aug. 2018 15:15, Oleg Cherkasov via samba wrote: >> >> This morning three of our FreeBSD-11.1-p11 servers with Samba 4.7.7 >> installations started to ignore ACL settings and reject user access to >> shares.  All three servers are members of DC running on Windows Server >> 2008R2.  Everything has

On 06. aug. 2018 15:15, Oleg Cherkasov via samba wrote: > > This morning three of our FreeBSD-11.1-p11 servers with Samba 4.7.7 > installations started to ignore ACL settings and reject user access to > shares.  All three servers are members of DC running on Windows Server > 2008R2.  Everything has been running ok for last few year.  I have been > upgrading Samba and FreeBSD

Hi, Has anyone had the following problem. Under Win2000 I copy a file from Windows Explorer to a share running samba 2.2.x. The file does not yet exist on the share however windows pops up a warning that the file already exists and it asks me to replace it. The thing is, the file has a size of 0 bytes. If I click "no" to not replace I end up with an empty file, otherwise it copies

On 10/16/06, Chris Diphoorn <chris.diphoorn@intouchdirect.com.au> wrote: > Can you help? Rsync's support for Windows ACLs is limited. What are you trying to do? Copy files from Windows to Windows, preserving Windows ACLs? If so, you might be better off using rsync to copy the files and another tool to copy the ACLs. Since rsync is meant first and foremost for Unix-like systems,

Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags)

I think the final support for ACL's in freebsd-5 is being added or has been already and the changes to the samba-devel port which will soon be renamed to samba22 will compile samba with acl support if you run make -DWITH_ACL as soon as that patch gets committed to the ports tree. This should happen pretty soon.

Hi I met problem developing plug-in under FreeBSD 6.1. First I tried to use internal plugins like quota and acl but I got: IMAP(xxx): module /usr/local/lib/dovecot/imap/lib01_acl_plugin.so: dlsym(acl_plugin_init) failed: Shared object "nss_dns.so.1" not found, required by "imap" This library doesn't exist on FreeBSD 6.1 Same story when u mention any plugin in

Hi, This morning three of our FreeBSD-11.1-p11 servers with Samba 4.7.7 installations started to ignore ACL settings and reject user access to shares.  All three servers are members of DC running on Windows Server 2008R2.  Everything has been running ok for last few year.  I have been upgrading Samba and FreeBSD installations and on last Friday upgraded to the latest packages from

Hi to ALL! I have dovecot-1.0r7 installed on FreeBSD 6.1, using kqueue and Maildir (<20 mailboxes, < 0,5 Gb size). Periodically CPU load of imap processes increasing up to 60-80%. Is it normall behavior or not? May be somebody had such kind of problems? -- ? ?????????, ?????? ????? ??? "???????" : ?????????? ??, WEB-?????????? +7 (495) 589 68 81 +7 (926) 575 22 11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On May 31st, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 5.5 is the last remaining supported release from the FreeBSD 5.x stable branch, support for the FreeBSD 5.x stable branch will also cease at the same point. Users of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On May 31st, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 5.5 is the last remaining supported release from the FreeBSD 5.x stable branch, support for the FreeBSD 5.x stable branch will also cease at the same point. Users of

First things first. Thanks to all samba developers and this great community. Some background info: I have a Samba 4.1.9 AD domain controller alone at the moment running on FreeBSD 9.2 with aprox. 50 clients, and a TS. The clients are mixed, mostly 7 and XP SP2. Due to a hard drive failure I ended up with a messed up db and a lot of problems, almost all of them including frequent panics in the

Hello, It appears that the FreeBSD port of Samba 3.0.x may be falling behind. The port maintainter does not use Winbind and thus has not kept up with the development of it. 3.0.1 will very shortly be ported to FreeBSD, currently it is still at 3.0.0. I know there have been some recent changes to Samba that help FreeBSD out, and I wanted to make sure that the port of Samba 3.0.x on FreeBSD stays

Hi all, I am playing with a test box at the moment running a Samba 2.2.7a domain on FreeBSD 5.0. I wish to enable ACLs, but I am not exactly sure what I am supposed to expect once they are enabled. I have created a UFS2 partition and enabled ACL support using tunefs. Since doing that, I have been able to connect to the Samba shares and modify ACLs, but so far the only things I have been able to

I have winbind working and it is providing security for my shares. Now, I would like to implement ACLs so I can help my backup users manage everything through MMC. Following is a copy of my smb.conf file. [global] workgroup = XX winbind separator = + idmap uid = 10000-20000 idmap gid = 10000-20000 winbind enum users = yes winbind enum groups = yes

The FreeBSD ACL implementation is currently based on a late POSIX.1e draft, and is similar in functionality to the ACL support in Solaris, IRIX, and Linux. It was developed along a similar timeline to the Linux ACL support, and Andreas and I chatted a fair amount along the way so the parallels are strong -- in fact, the Samba ACL support is almost identical, and the ACL API man pages on