similar to: multi-protocol (cifs/nfs) access to same files - help please

I'm trying to use zfs acls in solaris 10. I've looked at past posts regarding this and some online help, but am stuck. I'm currently using samba 3.3.9; I've had the same problem with 3.3.7. samba is compiled and running as an Active Directory member server (compiled with ldap and kerberos). The zfs disk is local. I'm not using winbind. I compiled with zfsacl module.

I think the issue may be related to the broken trusts. First of all only two people had specifically reported issues which meant for most people it was acceptable. Then I noticed that some directories seemed slower than others. If I ssh'd into the server and checked permissions, listing permissions on most directories was quick (under 2 second.) On directories that allowed

Does anybody have experience of running Samba on a domain and getting inherited file permissions on a Samba server to more closely match the permissions you would see on a Windows 2000 box? I'm trying to reproduce our departmental folders on a Samba box, running on ZFS with NFSv4 ACL's, but I'm struggling to get inherited permissions working properly when new files are created.

HI all, Having fixed the group issues from solaris having a default max of 16 groups I can now locally create and delete files on the solaris box as a domain user However when accessed via samba I can not create new files/folders (although I can delete the files I created when logged on locally) I have created a temporary directory on a non zfs (non acl enabled) file system to see if that

In our situation, we have users home directories on a zfs filesystem which are available from both nfs and via samba. One of our requirements is that we have to prevent users on the nfs mounted systems from being able to perform a chmod on their own home directory that allows other users access to their home directories. To this end we use ZFS ACLs such that we chown the user's home directory

There are definitely some files with some weird names- in an ssh session they don't even have regular characters. e.g -rw-rw---- 1 xxx xxx 114985112 Oct 31 14:39 ▒^t Not sure if that is related to problems though. The top command shows Memory: 12G phys mem, 343M free mem, 2048M total swap, 2048M free swap This is in the evening so should not be much load but I think

Hi I am accessing files in a ZFS file system via NFSv4. I am not logged in a root. File permissions look as expected when I inspect them with ls -v and ls -V I only have owner and group ACLs...nothing for everyone. bash-3.00$ id uid=100(timt) gid=10001(ccbcadmins) bash-3.00$ groups ccbcadmins staff bash-3.00$ ls -v testacl -rwxrwx---+ 1 timt ccbcadmins 0 Jan 31 16:24 testacl

On 02/12/2017 01:40 PM, Gordon Messmer wrote: > On 02/11/2017 08:56 PM, Robert Moskowitz wrote: >> This seems to be bug 1103439 which was 'fixed' for Centos6. >> >> What should I do about this? Is there a SELinux policy to apply or >> should I the avoid upd-ports option in Bind? > > > It looks like that bug was assigned to the selinux-policy

I've read there can be issues with /tmp so I switched the test to /var/tmp One file (foo.txt) is made by the shell user, while the other file (doo.txt) is made by the same user connected over Samba. bash-3.2$ ls -n doo.txt -rwxr--r-- 1 3000 3004 29 Jul 4 09:51 doo.txt bash-3.2$ ls -n foo.txt -rw-rw---- 1 61001 10 39 Jul 4 09:50 foo.txt With -l they both seem

On 02/11/2017 08:56 PM, Robert Moskowitz wrote: > This seems to be bug 1103439 which was 'fixed' for Centos6. > > What should I do about this? Is there a SELinux policy to apply or > should I the avoid upd-ports option in Bind? It looks like that bug was assigned to the selinux-policy component, where it was CLOSED NOTABUG, and then mistakenly marked CLOSED ERRATA. The

Right now, FreeBSD supports one type of ACLs - so called POSIX.1e ACLs. They are natural extension of the traditional Unix permissions, and for a long time were the only nonproprietary ACL type in Unix systems. Times change, and now there are several problems with them: they never actually become standard (the draft they are based on was withdrawn); this results in minor incompatibilities

Hi, I have a set of data (total number of record = 144,122), and I would like to use gamma-glm with log link to set up a model. IC is number of records IL is paid amount The table below shows that I have 30.578% of the data in the level of "1 - 1000" paid amount 20.320% of the data in the level of "1001 - 2000" paid amount and so on My question is could i use the whole data

This is my new Centos7 DNS server. In logwatch I am seeing: **Unmatched Entries** dispatch 0xb4378008: open_socket(0.0.0.0#5546) -> permission denied: continuing: 1 Time(s) dispatch 0xb4463008: open_socket(::#1935) -> permission denied: continuing: 1 Time(s) dispatch 0xb4464440: open_socket(::#8554) -> permission denied: continuing: 1 Time(s) dispatch 0xb4464440:

On Fri, 30 Jun 2017 11:13:25 -0300 francis picabia via samba <samba at lists.samba.org> wrote: > On Fri, Jun 30, 2017 at 10:26 AM, Rowland Penny via samba < > samba at lists.samba.org> wrote: > > > > > > > OK, What filesystem are you using ? > > > > > On Solaris /tmp is technically swap. > The partitions are generally set up as UFS, such

Daemon News is pleased to announce issue #7 of the print magazine. The Daemon News print magazine is an excellent resource for BSD sysadmins to read and use on the job, or just to have lying around the office for others to pickup and take an interest in BSD. The print magazine includes articles that have not appeared on the online ezine as well as really cool artwork that you won't see

Hi, this series cleans up the Python sources, either static or generated, including also tests, to make them PEP 8 compliant; see https://www.python.org/dev/peps/pep-0008/ and tools like pep8. Almost all the issues reported by pep8 are fixed, reducing the issues from 3818 to 7. The changes should have no effect on the actual code, while it will help Python users with consistency with other

Hi Karl, Thanks for your help, About the "Connection:" header, you are right, it's: "Connection: close" and NOT "Connection: keep-alive". The protocol when the SERVER sends the data is http 1.0. It's http 1.1 when the browser requests the data. I don't understand the "Content-Length: 54000000" header either. Also I noticed the flash player on