search for: file_cr

...8/01/30 19:05:18.064582,  5, pid=3294, effective(2002158, 2000513), real(2002158, 0)] ../source3/smbd/dosmode.c:206(unix_mode)   unix_mode: unix_mode(datatest/A/X/New folder (10)) returning 0770 Another efficient workaround could be to attach a simple script at some samba callback ( eg. file_created() ), but I don't know if exists such feature. I definitively too need to understand where the problem is because in my scenario I have a C folder readable only by domain users and writable only by some users but when such users create something there new files looks like the following...

Is behavior of ACLs under Samba 3.3.0 (Sernet) completely different from that under version 3.2.7? The release notes only talks about some "fixes". I installed version 3.3.0 and got completely different result with the same filesystem and the exact same samba configuration. The ACLs behaved strangely and appeared very different under Windows ACL editor. Users were now unable to

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''