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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
There are still a few tidyups of old FSF addresses to come (in both s3
and s4). More commits soon.
(This used to be commit fcf38a38ac691abd0fa51b89dc951a08e89fdafa)
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)
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)
- load our wins partners at start time:
# this is a sample partner record:
dn: name=SERNOX4-1,CN=PARTNERS
objectClass: wreplPartner
name: SERNOX4-9
address: 172.31.1.1
ourAddress: 172.31.9.1
type: 0x3
pullInterval: 3600
- go through all winsdb records in the database and create the wins_owner table,
but don't add ourself to it as out nbt task will update the db too, we refetch
the local max_versiion, each time we need it, (that typicaly onces per replication cycle)
metze
(This used to be commit 4490a2864e21f957547c30675e5f096a4409e5fb)
- open the winsdb in the wrepl server
- add dummy function for setup the replication partners
metze
(This used to be commit da3d18e4545da3bd1841ffc31f253e533f7ea016)
- w2k just ignores invalid packets, so we do now
- w2k only checks the assoc_ctx when the opcode has the sepcific obcode bit's set
- terminate the connection, when getting a WREPL_STOP_ASSOCIATION packet
- some more special error handling
proper torture test for all this cases are following later
metze
(This used to be commit 42b69461aad3942dde361d61b950445dd39882aa)
- move structs to a seperate header file
- move the code for the wreplsrv_in_call handling to a seperate file
metze
(This used to be commit c9a8544446312d96ecadcf370af76d9dc5b2531a)
