similar to: About CPU Affinity

Modified function runq_candidate in the credit 2 scheduler to have it consider hard and soft affinity when choosing the next vCPU from the run queue to run on the given pCPU. Function now chooses the vCPU with the most credit that has hard affinity and maybe soft affinity for the given pCPU. If it does not have soft affinity and there is another vCPU that prefers to run on the given pCPU, then as

in _csched_cpu_pick(), as not doing so may result in the domain''s node-affinity mask (as retrieved by csched_balance_cpumask() ) and online mask (as retrieved by cpupool_scheduler_cpumask() ) having an empty intersection. Therefore, when attempting a node-affinity load balancing step and running this: ... /* Pick an online CPU from the proper affinity mask */

If the domain''s NUMA node-affinity is being specified by the user/toolstack (instead of being automatically computed by Xen), we really should stick to that. This means domain_update_node_affinity() is wrong when it filters out some stuff from there even in "!auto" mode. This commit fixes that. Of course, this does not mean node-affinity is always honoured (e.g., a vcpu

Hi, Between Samba 3.4.15 and 3.5.11 there was a change in how 'wbinfo -r' gathers the groups of which a given user is member of. Assume there is a Windows 2003 domain called DOMA. This domain has a child domain DOMB. On DOMA there is a security group G-DL-DOMA which has domain local scope. On DOMB there is a security group G-U-DOMB which has universal scope. Group G-U-DOMB is member

Hello. I've got a samba4 domain member server. It works fine for the joined domain, but I'm not able to let user from a different domain get access. This worked fine on my samba3 member server, but I don't remember if I did anything special. I do have authentication set on the AD object for the users in question and we have a one-way trust with the other domain. All DCs are Windows

Hi All, Wonder is someone can help? We have mixed windows & Linux boxes in DomA network. Afaik all DomA clients are blocked and direct connection to DomB are not possible by design & for security. DomA DC(Windows) -- trust --> DomB DC(Windows) ^ | DomA Linux Client(DALC) winbind Samba 3.0.33 For some reason DomA Linux Client attempts ldap connection to all DomB DC once in 5 to 10

Hello all. I've set up a testing environment with two Windows DCs. The first, called DCA, is serving the domain DOMA and is running Windows 2003. The second is called DCB and serves DOMB on Windows 2008. The Samba machine I'm setting up (named ULYSSES) should be able to authenticate users from both domains for shell login. I've installed Samba 3.2.3 as a Debian package and closely

Hi, I am having difficuly deleting and renaming files with users from a foreign domain using acls. My setup is as follows : I have two Samba (3.0.14a)/LDAP domains connected via a VPN (OpenVPN) with a bi-directional trust relationship established. The trust relationship appears to be working correctly. I can log on onto PC's at either end on either Domain :) and the browse lists of both

If I create directory on the DomB DC named /test and create the following share: [test] path = /test read only = No acl_xattr:ignore system acls = yes DomA users can access that through Windows on DomB without issue, but if I set [sysvol] to "path - /test they cannot". There appears to be some special magic with [sysvol] I am unaware of. I'm not seeing any

The company I work for is split across two sites, each site has its own domain. The local end is a Samba server (DomA) with about 50 users, the remote end is NT4(DomB) with about 150 active users (400+ usernames in userlist). The two sites are connected over a VPN (Internally DomA=172.16.1.0/24, DomB=10.1.0.0/16) and the two domains trust each other. Users from either site regularly visit,

Hi everyone, I have two domains with a two way trust (DomA and DomB). When users from DomA (on a DomB Linux PC) access sysvol on DomB's DC using smbclient everything works: # smbclient //DomB /sysvol -Udoma\\user -c 'ls' -k . D 0 Thu Jan 9 13:53:03 2020 .. D 0 Thu Jan 9 14:28:29 2020 domb

Hallo. I have problem configuring winbind to authenticate against Active Directory (Windows Server 2003 R2 in native mode). Our net topology seems as follows: - We have PDCs for domain DOMA (i.e.) - there are user accounts for all people on our university. - We have PDC for domain DOMB (DC for our department) that holds computer accounts. - Between DOMA and DOMB is one side trust. So Windows

I'm currently building a Samba3-based domain (DomA) that has a trust relationship with an existing production NT4 domain (DomB). DomA uses an LDAP backend. The LDAP server is local on the PDC and is dedicated to such use. DomA runs Samba 3.5.6 on Debian 6.0. DomB is an old-timer: NT4 domain that's running for ages. The trust relationship has been established: DomA trusts DomB. Clients

Well, I'm attempting to migrate my old NT4-based domain to Samba3. I've got Samba set up with an LDAP backend, I've extended my NDS schema, and I've got users in this new domain set up successfully and authenticating. I've decided that the best, most seamless way to migrate my domain is to create a new domain which will run alongside the old domain. A two-way trust

I have 2 domains in my forest. I need to allow users from both DomA (The forest root and the Domain the server is joined to) and DomB to log in. All works fine with DomA, but no one from DomB can log in. wbinfo --domain=DOMB -u returns error looking up domain users. wbinfo -D DOMB returns the following: Name : DOMB Alt_Name : DOMB.local SID :

Hello, I did join 2 sites using an IPSEC tunnel, and made one domain trust the other (2 small Samba DC based domains with about 10 users in each) I first had resolving issues until I decided to keep only one WINS server for both networks (though this is still an issue to me because if for any reason the tunnel is broken, I have no longer WINS on one side). Finally here is my setup : Network A

Hello, we have a problem with the same userid's in different domains. we have to set the option "allow trusted domains = No" because winbind seens not beable to browse the hole AD (30 Domains over 20000 users). So everything is working fine like kerberos, net commands,.... Ticket name is [user1@DomA.net] [ 3151]: getpwnam DomA\user1 rpc: name_to_sid name=user1 name_to_sid

Hi, Trusting domain: DOMA Trusted domain : DOMB We are running samba-winbind 3.0.24 and have problems when authenticating user from a trusted domain (DOMB) (idmap backend = ad) in to DOMA. After some investigations, we found that when we are trying to login as a user from DOMB, it seems that sid2uid looks in own domain only, and fails to retrieve uid from sid. In DOMA: wbinfo -m shows the

Hi, I have two Windows Domains, DOMA and DOMB. A Samba 3.6 Server is a member server in DOMA. DOMA has a (unidirectional) trust relationship to DOMB. Users from DOMB should be able to connect and authenticate at the Samba server. The domain controller of DOMB has the IP 10.35.5.25. During authentication of a DOMB user at a share I get the following log entries: get_dc_list: preferred server

hi, it?s me again :( i?m still not able to use idmap_rid in a trusted domain environment (samba v3.0.20b Sernet). well, to be clear: NSS is not working (id, getent passwd <user>, ...) so samba does not find the posix information for any user from a foreign domain it?s working in a single domain with ##################################### # WINBIND - Settings idmap backend =