Reverted. Thanks for pointing this out.
Stefan (metze) Metzmacher wrote:
Am 24.06.2010 10:05, schrieb Matthias Dieter Wallnöfer:The branch, master has been updated via 41cdcd5... s4:provision.ldif - fix the number of available RIDs via fec489b... s4:provision.ldif - this Win2003 revision level seems always to be "9" on Windows Server 2008 machines via 64e19ef... s4:provision_users.ldif - change a group description to be correct via 560620a... s4:upgradeprovision - fix include order for "ldb" via e228b67... s4/ldb: ldb_msg_el_map_remote() should rename the remote attribute names into local names as defined in simple_ldap_map.c. via e88f37d... s4:setup/provision.reg - raise version to Windows Server 2008 R2 via b172b7f... s4:libnet_join.c - always use LDB constants from f34db12... Add parse_setjob_command() to make setting job state easier for users. http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master - Log ----------------------------------------------------------------- commit 41cdcd54b7b7e3fb70fdb220e74a1daf30e1891a Author: Matthias Dieter Wallnöfer<[email protected]> Date: Thu Jun 24 09:35:58 2010 +0200 s4:provision.ldif - fix the number of available RIDs There should be 4611686014132422209 and not 4611686014132422109. --- a/source4/setup/provision.ldif +++ b/source4/setup/provision.ldif @@ -809,7 +809,7 @@ dn: CN=RID Manager$,CN=System,${DOMAINDN} objectClass: top objectClass: rIDManager systemFlags: -1946157056 -rIDAvailablePool: 1001-1073741823 +rIDAvailablePool: 1601-1073741823 isCriticalSystemObject: TRUEI don't think that's correct. me...@sernox:~/devel/samba/ctdb/ctdb$ i 4611686014132422209 4611686014132422209 0x3FFFFFFF00000641 0377777777740000003101 0b11111111111111111111111111111100000000000000000000011001000001 me...@sernox:~/devel/samba/ctdb/ctdb$ i 0x641 1601 0x641 03101 0b11001000001 me...@sernox:~/devel/samba/ctdb/ctdb$ i 4611686014132422109 4611686014132422109 0x3FFFFFFF000005DD 0377777777740000002735 0b11111111111111111111111111111100000000000000000000010111011101 me...@sernox:~/devel/samba/ctdb/ctdb$ i 0x5DD 1501 0x5DD 02735 0b10111011101 changing it from 1501 to 1601 on a running system (the first dc already allocated its own rid pool with 500 entries) means changing the lower value by 100 and not by 600. The available pool also depends on the nextRid counter of the local sam, before the dcpromo. (which is copied into the 'nextRid' field on the domain object. The local dc account get the value of nextRid and the intial rIDAvailablePool starts with nextRid + x + 100. x was 0 in my dcpromo with a local rid counter of 500000. I'll test more combinations... I'm wondering why x is 1 in some cases and the rIDAvailablePool starts at 1101 when nextRid was 1000, instead of starting with 1100. Maybe it depends on the functional level. It also seems that the special dns accounts doesn't get hard coded rids, they're getting rids from the first pool the local dc allocates. metze metze
