IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
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)
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)
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)
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)
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)
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)
HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\WINS\Parameters\Prepend1BTo1CQueries
nbtd:wins_prepend1Bto1Cqueries=no will turn it off
metze
(This used to be commit 5362eede6b097c3a62d5c4d59151f8e26d89f1c0)
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)
parameter to (void *). void** in function parameters leads to type-punned
warnings.
Volker
(This used to be commit 57979d89c53b4363e4b447205703579df6756653)
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)
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)
