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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
changes
- use a periodic run interval of 15 secs per default, as we no longer
send push notifies with each run
metze
(This used to be commit 0382b3135c770847be33fbf8ee500f2c0bf265e2)
the call to winsdb_get_maxVersion() is moved into place.
This allows us to fetch records with the owner address that matches
our local_owner address, this is important if the restart with an empty wins.ldb.
w2k3 does this in the same way when you remove the database files from disk and restart
the WINS-Service.
metze
(This used to be commit e43de87d06614206a858e1102cd82e7f02163bba)
the difference between these at all, and in the future the
fact that INIT_OBJ_FILES include smb_build.h will be sufficient to
have recompiles at the right time.
(This used to be commit b24f2583edee38abafa58578d8b5c4b43e517def)
an uint32_t next_interval everywhere, we now call wreplsrv_periodic_schedule()
if we want to schedule an event
- also prevent us from looping with a 0 interval, by using 1s as minimum interval
metze
(This used to be commit b6943b11fc6e501d5081d591336185518943ee5a)
now $privatedir/wins_config.ldb contains the wins partners
and $lockdir/wins.ldb contains the name records
metze
(This used to be commit baa4a7a9d4f16adf476846850a63dfbfd51b10b3)
- for now we fake the change count to '1', so we'll still have periodicly triggered push
notifies, the interval is the 'wreplsrv:periodic_interval=60'
- add the 'pushUseInform' attribute to the wreplPartner objectClass
to configure if we'll use WREPL_REPL_INFORM notifies
metze
(This used to be commit fa1a5660bb2ef7fabd72ad9b993dd91d59ac409e)
system
- this needs to be in one big patch, because of the merging code,
that changes client in server connections and the other way around
- use socket_connect_send/_recv() in the client code
metze
(This used to be commit f0105b7fcdc3032d22444a1973927fff2dd9a06f)
instead make the normal composite_done() and composite_error()
functions automatically trigger a delayed callback if the caller has
had no opportunity to setup a async callback
this removes one of the common mistakes in writing a composite function
(This used to be commit f9413ce792ded682e05134b66d433eeec293e6f1)
- implement late release demands
we now pass the full NBT-WINSREPLICATION torture test
but only with non-socket_wrapper mode
metze
(This used to be commit bd78c97cfff7e2d3a053e4bb4d6459afad5fba5c)
(but only without socket_wrapper, I need to look at that later
and then add the different_owner test to NBT-WINSREPLICATION-QUICK
so that it'll be runned by make test)
metze
(This used to be commit 9ef33580345f12fafbab0a09644451c8b7600f7f)
- currently only the ADD, REPLACE and NOT REPLACE cases are handled complete
- other cases are just skiped for now
metze
(This used to be commit f889d110f5bcc0a19e110c63001e1aa4c18df870)
This patch changes the way lsb_search is called and the meaning of the returned integer.
The last argument of ldb_search is changed from struct ldb_message to struct ldb_result
which contains a pointer to a struct ldb_message list and a count of the number of messages.
The return is not the count of messages anymore but instead it is an ldb error value.
I tryed to keep the patch as tiny as possible bu as you can guess I had to change a good
amount of places. I also tried to double check all my changes being sure that the calling
functions would still behave as before. But this patch is big enough that I fear some bug
may have been introduced anyway even if it passes the test suite. So if you are currently
working on any file being touched please give it a deep look and blame me for any error.
Simo.
(This used to be commit 22c8c97e6fb466b41859e090e959d7f1134be780)
to make sure that replicas from the same owner are blinding overwritten
in all cases
metze
(This used to be commit 466baf737aedf240ff372ab8e8c708299102d1fa)
- add multihomed vs unique section
- update conflict handling for the above case
metze
(This used to be commit c043e56efd3d72cdd5b17c78512e12285c87f221)
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)
