similar to: Issue with acl_xattr:ignore system acls in 4.5rc2

On 08/18/2016 08:28 AM, Ralph Böhme wrote: > Hi Eric, > > On Wed, Aug 17, 2016 at 05:56:51PM -0600, Eric Eastman via samba wrote: >> I was testing Samba 4.5rc2 with an existing smb.conf file that I have been >> using since Samba 4.1.x and found that I cannot access data in the share on >> Windows 2012 (my AD server), a Windows 2008 client or on a Ubuntu 16.04 >>

Hi Eric, On Wed, Aug 17, 2016 at 05:56:51PM -0600, Eric Eastman via samba wrote: > I was testing Samba 4.5rc2 with an existing smb.conf file that I have been > using since Samba 4.1.x and found that I cannot access data in the share on > Windows 2012 (my AD server), a Windows 2008 client or on a Ubuntu 16.04 > client. I built a new version of Samba 4.4.5 using the same procedure as I

On 2016-08-18 at 12:21 +0300, Uri Simchoni via samba wrote: > On 08/18/2016 08:28 AM, Ralph Böhme wrote: > > Hi Eric, > > > > On Wed, Aug 17, 2016 at 05:56:51PM -0600, Eric Eastman via samba wrote: > >> I was testing Samba 4.5rc2 with an existing smb.conf file that I have been > >> using since Samba 4.1.x and found that I cannot access data in the share on

On Thu, Aug 18, 2016 at 12:21:37PM +0300, Uri Simchoni wrote: > On 08/18/2016 08:28 AM, Ralph Böhme wrote: > > Hi Eric, > > > > On Wed, Aug 17, 2016 at 05:56:51PM -0600, Eric Eastman via samba wrote: > >> I was testing Samba 4.5rc2 with an existing smb.conf file that I have been > >> using since Samba 4.1.x and found that I cannot access data in the share on

Hi Ralph, >> The line causing the problem with 4.5rc2 is: >> acl_xattr:ignore system acls = yes > > this change was introduced in > <https://bugzilla.samba.org/show_bug.cgi?id=12028> > > Before explaining the gory details, one question: why are you setting > this option? I am setting this option per the vfs_acl_xattr.8 man page recommendations. Using a

Hi Eric, On Thu, Aug 18, 2016 at 07:57:36AM -0600, Eric Eastman wrote: > >> The line causing the problem with 4.5rc2 is: > >> acl_xattr:ignore system acls = yes > > > > this change was introduced in > > <https://bugzilla.samba.org/show_bug.cgi?id=12028> > > > > Before explaining the gory details, one question: why are you setting > >

On Wed, Aug 24, 2016 at 04:06:42PM +0200, Ralph Böhme via samba wrote: > > Yeah, as much as I'd like to avoid adding a new option, I guess we > have to do something about it, my latest take on this is > > acl_xattr:default acl style = [posix|windows] > > This parameter determines the type of ACL that is > synthesized in case a file or

On Thu, Aug 25, 2016 at 12:14:00PM -0700, Jeremy Allison wrote: > On Wed, Aug 24, 2016 at 04:06:42PM +0200, Ralph Böhme via samba wrote: > > > > Yeah, as much as I'd like to avoid adding a new option, I guess we > > have to do something about it, my latest take on this is > > > > acl_xattr:default acl style = [posix|windows] > > > >

On Fri, Aug 26, 2016 at 09:39:29AM -0700, Jeremy Allison wrote: > On Fri, Aug 26, 2016 at 06:33:26PM +0200, Ralph Böhme via samba wrote: > > On Thu, Aug 25, 2016 at 12:14:00PM -0700, Jeremy Allison wrote: > > > On Wed, Aug 24, 2016 at 04:06:42PM +0200, Ralph Böhme via samba wrote: > > > > > > > > Yeah, as much as I'd like to avoid adding a new option,

On Fri, Aug 26, 2016 at 06:33:26PM +0200, Ralph Böhme via samba wrote: > On Thu, Aug 25, 2016 at 12:14:00PM -0700, Jeremy Allison wrote: > > On Wed, Aug 24, 2016 at 04:06:42PM +0200, Ralph Böhme via samba wrote: > > > > > > Yeah, as much as I'd like to avoid adding a new option, I guess we > > > have to do something about it, my latest take on this is >

On 2016-08-18 at 12:40 +0200, Ralph Böhme wrote: > Hi Michael, > > On Thu, Aug 18, 2016 at 11:42:12AM +0200, Michael Adam wrote: > > From reading the original post, I get the impression > > that the problem is associated to the share root directory. > > nope. It will happen with just any directory or file created from a > non SMB client, eg mkdir|touch (or NFS, ...)

Hi Michael, On Thu, Aug 18, 2016 at 11:42:12AM +0200, Michael Adam wrote: > From reading the original post, I get the impression > that the problem is associated to the share root directory. nope. It will happen with just any directory or file created from a non SMB client, eg mkdir|touch (or NFS, ...) on the server. It is also associated with files or directories created from Windows

Hi List, we're calling a sip phone from our Asterisk Server, and try to add logic depending on the dialstatus Stripped down example; exten = 494XXXXXXXXX,n,Dial(SIP/4120089,15,w) exten = 494XXXXXXXXX,n,Goto(98-${DIALSTATUS},1) exten = 494XXXXXXXXX,n,Hangup() ..... exten = 98-BUSY,1,NoOp(Busy) exten = 98-BUSY,n,ExecIf($["${Voicemail}" =

Dear All, I have the data some thing like this, I am showing here three days data only: > dummy.data <- read.table(file='dummy.txt',sep='', header=TRUE) > dummy.data StDate Domaindesc Logins 1 05/01/10 xxx 10 2 05/01/10 xxx 45 3 05/01/10 xxx 2 4 05/01/10 yyy 45 5 05/01/10 yyy 20 6 05/01/10 yyy

Hi, I''m having an issue with changing the source address of packets origininating from a specific user using a combination of iptables and iproute2. We want to change packets originating from a specific service so that they originate from that service''s IP address, so that we can move it to a different physical server and have the packets appear to come from the same

Trying to use R to build an interactive "slide show", to be displayed on a projector. The purpose of the presentation is to show how one could construct a simple graph using R. It is meant as a general overview rather than as detailed instruction. For example, something like the following sequence of commands. At lecture time, I want the interpreter to read these commands one at a

Dear all, I am trying to split a matrix into 2 as efficiently as possible. It is a character matrix: 1 2 3 1 "2-271" "2-367" "1-79" 2 "2-282" "2-378" "1-90" 3 "2-281" "2-377" "1-89" I want to make 2 matrices from this, as succinctly and efficiently as possible. I've tried such

See the following SIP trace. Where in the world does Asterisk get port 1025 to respond to? This is asterisk 1.6.x. Thanks. -- James <--- SIP read from zzz.zzz.zzz.44:9363 ---> NOTIFY sip:pbx1.mydomain.com SIP/2.0^M Via: SIP/2.0/UDP 192.168.1.140:9363;branch=z9hG4bK-b9a860d3^M From: "xxx-xxx-xxxx" <sip:xxxxxxxxxx at pbx1.mydomain.com>;tag=467525dd6fac949do0^M To:

Hi Peter, I got all your patches and applied them, and I wanted to say kudos for a great job done. This is the output of upsc that I'm getting right now. I had the same issue when using any cvs version (from two weeks ago) that made my UPS go into a state where it wasn't functioning normally (checking the kernel log shows that it cannot be connected and I had around a page of DEVFS_USB

I have the following list of strings: name <- c("hsa-miR-555p","hsa-miR-519b-3p","hsa-let-7a") What I want to do is for each of the above strings replace the text after second delimiter with "zzz". Yielding: hsa-miR-zzz hsa-miR-zzz hsa-let-zzz What's the way to do it? [[alternative HTML version deleted]]