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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
- as the old records are broken sinse the last winsdb_dn() changes, (the dn components order was reversed)
we can use nicer attribute and objectClass names...
- use much more verbose error handling for winsdb_*
- print a debug message when we found a corrupted record
metze
- 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
- 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 is the start of a WINS-Replicaton server:
The design is to handle incoming and outgoing connections,
in one process, because it make thing much easier, and there's
no need to it otherwise.
The current code only parses incoming packets, and can reply
to them, but currently only a standard error packets STOP_ASSOCIATON
with reason == 4 (I think it means your are not configured as a wins partner of me)
(the server service is called "wrepl")
metze
