Age | Commit message (Collapse) | Author | Files | Lines |
|
Please check!
For code symmetry reasons, trans2 might also see this fix, but this is left to
the interested reader :-)
Volker
(This used to be commit f2d364ebe69fc5d624e456cc7d941071811a5567)
|
|
Andrew Bartlett
(This used to be commit c3977b4bae1e1b5e4ff4a64c7146534536685e91)
|
|
(This used to be commit 38b688fd15a9103e5ef5c86e01b594169d6b6b9c)
|
|
Fix the join code to know that the ldb layer handles the keytab update.
Andrew Bartlett
(This used to be commit d3fbc089f4161ae71b21077d50130fdabd8b2d77)
|
|
matching va_end() for each va_copy(). This doesn't matter for most
architectures, but there could be some obscure ones where it does
matter.
some of this should be ported to Samba3
(This used to be commit 21eb316473486cb6b73bb3ff9c5f3a44ecd57e4a)
|
|
complex once we have code for changing the number of nodes)
- fixed a ctdb/tcp bug in the handling of multiple packets waiting on
a socket
(This used to be commit faf9a1146cb5f33228a11e01b66cb3cbe18bd05d)
|
|
(This used to be commit 2d6e082e813e18dcd43bc8d9a8f445f77e0a8452)
|
|
If this happens:
- two sockets are readable, and select/epoll/aio returns both of
them
- read event on socket1 is called
- inside that read event an event_loop_once is called, this returns that
socket2 is readable
- read event on socket2 is called
- event_loop_once returns
- top level event handler then calls read event on socket2 (as it
still has that listed as readable)
- read handler for socket2 returns zero byte read, which is
interpreted as end of file
- socket is incorrectly closed
this happened with ctdb, but it could happen anywhere (just
rarely). The fix is trivial - ensure we break out of the event loop
when we have been called recursively.
(This used to be commit e042002bb5ee8974220e1ade56b64389571f75a6)
|
|
metze
(This used to be commit 1f8a037ac4f592d29f7d66e1f924efe1c5d8c2b0)
|
|
(This used to be commit 3f41a4b014a47b3c751066f5d1bef7f76f4be831)
|
|
locks retry immediately when another blocking lock is removed.
(This used to be commit 169920a5341392e84d5b5fb5f39c2b9d5243bb3b)
|
|
early byte range lock retries (ie. PENDING locks in brlock)
(This used to be commit 09237e3acf524f7e772acce2e652ef30b8ba4d65)
|
|
them as a hook on ldb modify, via a module.
This should allow the secrets.ldb to be edited by the admin, and to
have things update in the on-disk keytab just as an in-memory keytab
would.
This isn't really a dsdb plugin, but I don't have any other good ideas
about where to put it.
Andrew Bartlett
(This used to be commit 6ce557a1aff4754d2622be8f1c6695d9ee788d54)
|
|
(This used to be commit 966c30ca591c410a4a229396c7919fe8f98bd066)
|
|
acceptable.
In Samba3 with inotify we have the problem that the MODIFIED action is sent
second. I think this could also happen in Samba4, depending on the order when
the different sockets (unix domain dgram / inotify) are looked at by the
events system.
This patch accepts the NEW/OLD/MODIFIED entries in any order.
Comments welcome!
Volker
(This used to be commit 72a7771b757c3aca637eb632abebab60bdd2da9f)
|
|
Volker
(This used to be commit c9886ce63b8cc085e0032ad2f6193c547336856d)
|
|
(This used to be commit 3548b1f683a7f5ccc6563de7e099d3a5a86ed39c)
|
|
metze
(This used to be commit dfbdb958419a041c1aff039810f7e9cb4320ec2c)
|
|
HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\WINS\Parameters\Randomize1CList
nbtd:wins_randomize1Clist=yes
nbtd:wins_randomize1Clist_mask=255.255.0.0
metze
(This used to be commit eee635ab4d7ae8ffd8962b3d4518a7e6b5a90f97)
|
|
metze
(This used to be commit 1c942b7d8ffb97b70f17fd901033f54771274b96)
|
|
current code in Samba 3 is already generated using this pidl patch.
(This used to be commit 30a06273d28fb59c6f20154f97c67f4c0a63dee9)
|
|
metze
(This used to be commit e788709835fa13b512fbf38951c9d0ca9bc3df18)
|
|
Andrew Bartlett
(This used to be commit 1c466c6d6f02bf76f7f68e7dcd3d9a4c2a63179a)
|
|
LDAP implementation, and another to hold the key blobs.
Also fix the OpenLDAP test.
Andrew Bartlett
(This used to be commit ec511c592bbb7df513fe6f62e06e1fa984431550)
|
|
We can't actually use it, as we are stuck inside our socket_wrapper
network, and can't talk to it.
Andrew Bartlett
(This used to be commit bd564da6b9b45c438ef81b42dc156116ed81cbe7)
|
|
(This used to be commit 54b63787606f392e094fe28c2536999c34f76f44)
|
|
HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\WINS\Parameters\Prepend1BTo1CQueries
nbtd:wins_prepend1Bto1Cqueries=no will turn it off
metze
(This used to be commit 5362eede6b097c3a62d5c4d59151f8e26d89f1c0)
|
|
(This used to be commit 7512270ffae4e72d70f6ca347f09708f1bf915ad)
|
|
rather than allocating a reply_data field each time, I have changed
the ctdb_call API to include a status code. That greatly simplifies
use of the API.
(This used to be commit 70c3acaf8876fa5712e2135df234fe3bc1e32e77)
|
|
- convert brlock code to new API
(This used to be commit cf317480cb715dbaab87c06f824a1db14b09b298)
|
|
Andrew Bartlett
(This used to be commit 92cea0b79011e9b86ab7e782c83ad5964a5925bd)
|
|
(This used to be commit eb83537a3b4889353cdc9bb471315a77e1f87c90)
|
|
function
parameter to (void *). void** in function parameters leads to type-punned
warnings.
Volker
(This used to be commit 57979d89c53b4363e4b447205703579df6756653)
|
|
(This used to be commit afe0d170b08deb712b91ee73cc00a444e989b480)
|
|
Andrew Bartlett
(This used to be commit 76812a0337fbfcb19939c6ee7a57975b6d690a4d)
|
|
(This used to be commit 6713945fbab2df5b695c11df623f16d0abd1a772)
|
|
(This used to be commit 65cb965f11534a0636ab083219d84eb78dceecae)
|
|
(This used to be commit 7b160f18b26a5abe13b1cbc8039e57bd0cee86e0)
|
|
(This used to be commit 2c6cc617f9cc84c1cd9f6652d3a8ac9c605ab42c)
|
|
- Use --list option for smbtorture for local and nbt tests as well
(This used to be commit 053d5a40bc96b9503220f17f59677a0df6677a1e)
|
|
(This used to be commit 7de4727ceb5935dd5fca49db0331c4509f735362)
|
|
Andrew Bartlett
(This used to be commit 5e907ae795b49d6c120ddedee3ba6d11c06bfab4)
|
|
tarball.
Andrew Bartlett
(This used to be commit 59752290438f9a1a10d81f798e1e9746508e4d5a)
|
|
recipe.
(This used to be commit b975ce3a471d29fb2c0691c65993f9dfeb066d79)
|
|
To automaticly test this, we need to decide if we should ship kinit
(and possibly and hxtool).
Andrew Bartlett
(This used to be commit 413df7114e194b9c081d53ef29d42743129ad518)
|
|
standalone and built-in ctdb
(This used to be commit 3e5f29bddfd83914eeec706367b2b1bd30aba31e)
|
|
(This used to be commit 6af4557b1306e7e6a23c697cef3467d0f0458531)
|
|
this is part of the solution to LOCAL-EVENT on fort
(This used to be commit 35f62bc12559e355d4ac73018afe255ea7c5866b)
|
|
of KDC behaviour. This should allow PKINIT to be turned on and
managed with reasonable sanity.
This also means that the krb5.conf in the same directory as the
smb.conf will always have priority in Samba4, which I think will be
useful.
Andrew Bartlett
(This used to be commit a50bbde81b010bc5d06e3fc3417ade44627eb771)
|
|
I think this happens when both are eventual children of the autofree context.
(Trying to track down a valgrind error on fort).
Andrew Bartlett
(This used to be commit aee751497ca738fa0de72dd0748590a74d5af2fd)
|