Age | Commit message (Collapse) | Author | Files | Lines |
|
- add multihomed vs unique section
- update conflict handling for the above case
metze
(This used to be commit c043e56efd3d72cdd5b17c78512e12285c87f221)
|
|
- print "supplementalCredentials" also when --option="dssync:print_pwd_blobs=yes"
is used
abartlet: this field may contain the krb5 keys...
metze
(This used to be commit 26c69348ca3ae10128df9832f8b4d9c1024631e2)
|
|
find the file it tries to use (build/tests/ftruncroot.c) and the value
it defines is not used anywhere.
(This used to be commit 97bbf4a46035becaee50d242364146e3529cf631)
|
|
Config module instead of the configure-generated config.pm on case-insensitive
filesystems (MacOSX, OpenVMS)
(This used to be commit 47b8095a0a0e7f352860999df3b131cab3e8a2b9)
|
|
because
--user-sids required the extension to trusted domains.
Implement "winbind sealed pipes" parameter for debugging purposes.
Volker
(This used to be commit 3821a17bdb68b2f1389b5a150502c057d28569d2)
|
|
handle a UTF16 string in a uint8 array
metze
(This used to be commit d13315f3b135228febcbe9b99d3550363c21da81)
|
|
to our winsrepl server, but it handles only the simple cases (without merging)
and we still didn't apply records to our wins.ldb, we just print out what we would do
metze
(This used to be commit e4edeeaa0a808c6bcdf022eec1257e796c1c0700)
|
|
ACTIVE vs ACTIVE
ACTIVE vs TOMBSTONE
RELEASED vs ACTIVE
RELEASED vs TOMBSTONE
TOMBSTONE vs ACTIVE
TOMBSTONE vs TOMBSTONE
as it seems that is all we need to test,
and w2k3 only decides between ACTIVE and NON-ACTIVE (REALEASED or TOMBSTONE)
when it gets new replica objects
also I have removed all the extra test, we only test the worst cases now,
and this will make the algorithms more clear when you look at the output
of the NBT-WINSREPLICATION torture test
metze
(This used to be commit 7545e4e7160864f5feedd35cf90507e47d7cf469)
|
|
metze
(This used to be commit 62ddca0e1f3d7484b32df7f5a56eca4761289c00)
|
|
metze
(This used to be commit 891416b79eeec3d6c9391181f86b104b887774a2)
|
|
- disable special group vs. special group,
I need to look closer at this, as I'm getting strange timeouts
randomly, so the server might be doing some challegnes while
doing the merging of special group records, witch reaches
timeouts
metze
(This used to be commit 7479760cbf5fe818c31b7795dc43b413800a63bd)
|
|
metze
(This used to be commit d8e7e914bf29f7ae0b7cc1f47ea9f8cca210d8df)
|
|
metze
(This used to be commit ba2c100be6eb1d352df762d213fc197f11f69da5)
|
|
metze
(This used to be commit 0d948cf430f34757a17170cdd26ac6b87341a75f)
|
|
metze
(This used to be commit 9903a47151a96177e835ba45450ad12a2e969ee2)
|
|
metze
(This used to be commit 03a8ff89d0f40eed3a8e0f94d2e756d9c648b564)
|
|
metze
(This used to be commit ba1727623675def77d4bf3a9bf643f80c7e168c2)
|
|
(This used to be commit 55805b5ed9493160ff17c26d2e1361947f368707)
|
|
(This used to be commit 449cc714b882d6ebea3e1cbf92e204efba98b6cb)
|
|
- make sure we test the worst case,
so that we don't need to test everything...
- same ip(s) => not replace
- different ip(s) => replace
metze
(This used to be commit 4a22ce09b4cad7bb3d60e45f25fb19c36efb8dec)
|
|
the right
talloc context.
Volker
(This used to be commit 256cf928d786b2533953505aea20ec80a25c6929)
|
|
metze
(This used to be commit 13703b5c35e4473d0ab6b595f41f4cc35c18f81e)
|
|
metze
(This used to be commit 9a7689c745e9fa9f40c46fa041a502967fd93ccc)
|
|
- add unique vs. multi homed section
metze
(This used to be commit 7f8c26cd33a5dffd672d0995cf227177bc21a20e)
|
|
metze
(This used to be commit 980e1a39eb039ebef3ca750eaf67bb87fd6f6980)
|
|
- added nicer error display, giving a string version of the error code
(This used to be commit 5ec486bb81536b38a5f40cae7555cbcbbfa52263)
|
|
- randpass() is now in the random ejs module, not global
- don't dereference the undefined variable on getopt failure
(This used to be commit 7e338c23f5ac351b362a9e07fd81ec07bc700484)
|
|
PDC. I suspect we should behave slightly differently on the two ports,
but this is a lot closer than not listening at all. When creating a
user with mmc the global catalog port is used to check for an existing
user
(This used to be commit f8430c3f41313d0a71cea23e1a2ef98f088aff44)
|
|
(This used to be commit e28a334eeb8fa22f686d0c1dc48b2977d85b9e10)
|
|
(This used to be commit b6e8018a3b2326c3d1df4811a0581c5c0967bfd3)
|
|
ldb_transaction_cancel() broke it)
(This used to be commit dc41994ea72c7c7f571efa009930cf36d7a9897a)
|
|
- check that the record is the same as what we pushed to the server
(we need to verify the ip-addresses later too...)
metze
(This used to be commit f59e90299d1060a3c61ee24bdf4a2a13aac1bccf)
|
|
(This used to be commit 407df9628e383822680af766dd94532e59397382)
|
|
the same spot (it has identical TCP sementics).
Andrew Bartlett
(This used to be commit 84d6118e8762608af0945279d80ad0f898e693d9)
|
|
Support conformant [string] arrays
Eliminate utf8string
This breaks xattr binary compatibility with previous versions - is that a
problem?
(This used to be commit 7596c708ba6642473319a1b699a5a910a639e50d)
|
|
(This used to be commit 22d0e4a9bf853fe67c402ce3ba6d950e753ab4d2)
|
|
(This used to be commit c8a0511f37f8cff3e949ffda0bb7fae714d5bbb4)
|
|
(This used to be commit bb1ed44f45020f1e11d928f5130a889c11ee59c4)
|
|
(This used to be commit 7e057e6bdaf82bf8acdfc5d656dd75f367e70bf2)
|
|
(This used to be commit 48f45927ceb4f7d39c4cc47b3b843e43a53b7f2b)
|
|
(This used to be commit 6a8291c80ee814a6bdc092b3ef53f450f30b44a0)
|
|
(This used to be commit 1ac8c96349c1241f75f7a133cfefa0df5aaae18e)
|
|
(This used to be commit 88fcd56fb55ac3f7e1eef3b3c92a2593c79599d3)
|
|
(This used to be commit b773d848e854394f36351f97130a20a245367b2c)
|
|
Tridge, if you have the time, you might want to look at a problem I'm having
with unix domain stream sockets. From a comment in this commit:
/* Using composite_trigger_error here causes problems with the client
* socket. Linux 2.6.8 gives me a ECONNRESET on the next read after
* writing the reply when I don't wait the 100 milliseconds. */
This is in winbind/wb_cmd_userdomgroups.c:93.
The problem I have is that I can not *immediately* send an error reply to the
client because the next receive fails. Waiting 100 milliseconds helps. It
might also be a problem with epoll(), I don't really know.
I'd appreciate if you took a brief look at this, maybe I'm doing something
wrong.
Thanks,
Volker
(This used to be commit 3e535cce743710a68a4264e4f66e9c0c4d6770c6)
|
|
(This used to be commit a14398715eceecf204caf815a8769ba8214d0576)
|
|
initialized, do that
first. And if a request is being processed, queue it. This correctly survived
3 endless loops with wbinfo's doing different things while starting up smbd.
The number of indirections starts to become a bit scary, but what can you do
without a decent programming language that provides closures :-)
One thing that we might consider is to auto-generate async rpc requests that
return composite_context structs instead of rpc_requests. Otherwise I'd have
to write a lot of wrappers like composite_netr_LogonSamLogon_send.
The alternative would be to write two versions of wb_queue_domain_send which I
would like to avoid. This is cluttered enough already.
Volker
(This used to be commit 66c1b674f9870de73cce0e611909caf9eff34baa)
|
|
metze
(This used to be commit 2577c02a5105449b759e7eeb00c446730dbe22d3)
|
|
server
metze
(This used to be commit 772467c8d487578b3541ffd1b1e07516097d1325)
|
|
metze
(This used to be commit 3f7b09a3086a8b6d255bc3fc5cd8882e12f05d10)
|