similar to: Renaming a domain computer

Dear Tomas, thank you for looking into this. Here's the output: # number of logical processors - what detectCores() should return out <- system("wmic cpu get numberoflogicalprocessors", intern=TRUE) [1] "NumberOfLogicalProcessors \r" "22 \r" "22 \r" [4] "20 \r"

Dear Tomas, thank you very much. I installed r-devel r75201 and tested. The machine with 88 cores has NUMA disabled. It therefore has 2 processor groups with 64 and 24 processors each. require(parallel) detectCores() # [1] 88 This is great! Then I went on to test with a simple 'foreach()' loop. I started with 64 processors (max limit of 1 processor group). I ran with a simple function

IMHO, in short, learn to use encrypted connections. 2016-07-27 22:38 GMT+02:00 Kris Lou <klou at themusiclink.net>: > As of 4.2.11: https://www.samba.org/samba/security/CVE-2016-2112.html > > =================== > New smb.conf option > =================== > > ldap server require strong auth (G) > > The ldap server require strong auth defines whether the

Dear R-devel list, R's detectCores() function internally calls "ncpus" function to get the total number of logical processors. However, this doesnot seem to take NUMA into account on Windows machines. On a machine having 48 processors (24 cores) in total and windows server 2012 installed, if NUMA is enabled and has 2 nodes (node 0 and node 1 each having 24 CPUs), then R's

So you have to reset the other account flags after doing it? On 08/15/2019 02:43 PM, Kris Lou via samba wrote: > pdbedit -c="[]" <user> > > This clears the Account Flags (warning, clears ALL Account flags) that you > can also view via "pdbedit -Lv <user>" > > > Kris Lou > klou at themusiclink.net > > > On Thu, Aug 15, 2019 at 12:11

Dear Arun, thank you for checking the workaround scripts. I've modified detectCores() to use GetLogicalProcessorInformationEx. It is in revision 75198 of R-devel, could you please test it on your machines? For a binary, you can wait until the R-devel snapshot build gets to at least this svn revision. Thanks for the link to the processor groups documentation. I don't have a machine

I have a bit of an oddity here: I'm using Samba 4.2.14 with AD, using Samba's internal DNS to serve to my domain (and forwarding others to Google Public DNS 8.8.8.8). However, it looks like client queries (and subsequent forwards) to a vendor's URL (www.pitneybowes.us) fail, but are successful if I query Google directly: [root at XXXX~]# nslookup -type=any www.pitneybowes.us >

Hi all, I seem to have run into a case where my DC's aren't being round-robin'ed by DNS. I've got 3 DC's using Internal DNS, but every time I ping mydomain.com and check the results (ipconfig /displaydns), it's always in the same order. The same order appears when I query the DC's directly, individually: # nslookup mydomain.com 172.23.51.5 Server:

On Wed, Dec 27, 2023 at 12:21?PM Sonic <sonicsmith at gmail.com> wrote: > On Wed, Dec 27, 2023 at 2:31?PM Kris Lou via samba > <samba at lists.samba.org> wrote: > > > named.conf.local > > > ===================== > > > include "/usr/local/samba/private/named.conf"; > > > ===================== > > > > Is the correct

I've found that some embedded devices have older CIFS clients, which can only talk over SMB1. So, you can adjust your server to allow it, or look for another file transport. Kris Lou klou at themusiclink.net On Wed, Sep 9, 2020 at 3:16 PM Jeremy Allison via samba < samba at lists.samba.org> wrote: > On Wed, Sep 09, 2020 at 02:35:28PM -0700, Peter Pollock via samba wrote: >

A summary for reference: the new detectCores() for Windows in R-devel seems to be working both for logical and physical cores on systems with >64 logical processors? (thanks to Arun for testing!). If the feature is important for anyone particularly using an older version of Windows and/or on a system with >64 logical processors, it would be nice if you could test and report any

Perhaps try http://wing-repo.net/ for CentOS rpms? The readme is out of date -- inspecting the repo at http://wing-repo.net/wing will find 4.6, 4.7 (in extras), 4.8rc3. Kris Lou klou at themusiclink.net On Wed, Feb 21, 2018 at 8:27 PM, denis.shigapov via samba < samba at lists.samba.org> wrote: > We have the standard centos. > I have recompiled packages from Fedora, as well as all

> > There is also Citrix XenServer for maxium > comfort. It offers GUI tools under Windows for managing VMs. The > drawback is, there are a lot of parameters you cannot set in the non > paid version. Just to throw it out there, there's also XCP-NG which is a rebranded (w/o Citrix) version of XenServer without all of the proprietary bits. The same people also produce

piggybacking on the "Syncing Sysvol" thread ... I had thought that the conventional wisdom was that ntacl sysvolreset should be mostly avoided once relative stability achieved and additional GPO's created. https://wiki.samba.org/index.php/Sysvolreset Has this changed recently? Kris Lou klou at themusiclink.net

You're geniuses one and all! That looks to have fixed the problem! At a later date I'll try to work out how to do it via ftp so I can avoid the smb1 protocol altogether, but for now I have a working solution so THANK YOU! On Wed, Sep 9, 2020, 3:45 PM Andrew Bartlett via samba < samba at lists.samba.org> wrote: > The other thing is NTLMv2, also required by default in modern

Shanks for the hint! Very strange that the default is only to use a deprecated protocol… Anyway, this option has no effect on this issue… Yvan Le 31/05/2019 à 18:53, Kris Lou via samba a écrit : > Most likely, your Windows 10 (file server) is disallowing SMB1 connections, > which is the default for smbclient. > > You can force smbclient to use a higher protocol with "smbclient

Hi Rob, I'm not sure you will get much pleasure out of VirtualBox on that hardware. It sits completely on top of the OS and it will grab most of the resources, even hogging from the OS. And it will run very hot. The Xen hypervisor (incl. XenServer, XCP-NG) is very resource efficient and with Linux guests (PV or PVHVM), it will run very smoothly. The same applies to KVM. My FX-6300 box

Dear Arun, thank you for the report. I agree with the analysis, detectCores() will only report logical processors in the NUMA group in which R is running. I don't have a system to test on, could you please check these workarounds for me on your systems? # number of logical processors - what detectCores() should return out <- system("wmic cpu get numberoflogicalprocessors",

Previously, I needed to downgrade Louis samba packages to Buster's defaults, which would then be upgraded to 4.13 by the dist-upgrade to Bullseye. This was on a Domain Member, so didn't touch my DC's or have to worry about DB format stepping (I hope). apt install samba=2:4.9.5+dfsg-5+deb10u3 python-samba samba-common=2:4.9.5+dfsg-5+deb10u3 samba-common-bin=2:4.9.5+dfsg-5+deb10u3

So, I'm using Samba AD for user authentication by some web appliances, using LDAPS over port 636. I've been doing this for quite a while -- and my certificates and everything seem to check out. But this week (and with one appliance -- my firewall), I'm finding that maybe 3/20 times the bind will fail for perhaps 10 seconds. During this time, the logs read (for each failure):