search for: unproper

...for(each pair of univariate time series) { > if(is.null(ylim)) { > ...#set ylim properly > } > ... > } > > in plot.acf code, so that in the first iteration the ylim par is properly > set to about c(0,1), but in > subsequent interations, ylim is no more NULL, and the old, unproper ylim > specification > remains. Thanks for noticing this. It's easy to fix, but before I do, I'd like an opinion on the proper fix. Should all the plots use the same ylim, or in the case where it is unspecified, should they each choose their own? I can see arguments for both po...

On Tue, 12 Sep 2017 19:30:42 +0100 Miguel Medalha via samba <samba at lists.samba.org> wrote: > Your problem probably comes from using the AD DC as a file server. > The file server should be separated, as recommended by the Samba > team. I get close to wire speed on dedicated member servers. > > With version 4.4.2, changes in behaviour for the "server signing" and

Hi Rowland The 4.5.10 was the newest of 4.5x series on that time, but the 4.5x series is still supported isn't it ? What shares are configured unproperly or like old samba way ? ----- Original Message ----- From: "samba" <samba at lists.samba.org> To: "samba" <samba at lists.samba.org> Sent: Tuesday, September 12, 2017 3:50:56 PM Subject: Re: [Samba] SMB data transfer performance on AD mode On Tue, 12 Sep 2017 1...

...and get connection. In our command all ISO characters are properly mapped to CP852 ones. But if we now execute dir command, the result will be completly unreadable. All filenames with CP852 characters will be distorted - some of them will vanish, others will be mapped unproperly. To examine the problem more closely, one can use below command to save share's listing in a file: ./smbclient //PCNAME/ISO8859-2_share -c dir > PC.dir After opening PC.dir in vi editor we will see that characters (for example) 0x88 and 0xa5 from CP852, are mapp...

I have a question on how to handle the "h" routines. I have noticed that if the call is hung up by the side that originated the call, the "h" routine is not extendable via a macro, or at least I have been unable to do it. My tests have included only SIP->SIP calls. If the originating side hangs up first: The macro is called from "exten =>

...ne here solved this ? For me it looks like XP workstation loosing it's browser or perhaps another machine wining election ( even two LMB in one network segment!). Is there any way of debugging tis from M$ side ? Should i supply wiresharck dump or another information? If you find this post unproper for this list please let me know. I'll try another. Big THANKS Looking forward for hearing from You Thanks in advance Sorry for mine poor english ... Bartek R.