summaryrefslogtreecommitdiff
path: root/source4/wrepl_server/wrepl_server.h
AgeCommit message (Collapse)AuthorFilesLines
2007-10-10r12434: implement database scavenging, the only missing part is the ↵Stefan Metzmacher1-0/+32
verifying of active replicas with the owning wins server, after the verify interval passes. metze (This used to be commit 7d1f7ae9c65c09f8bf72e159b771f231f96e8591)
2007-10-10r12391: use the new periodic schedule system for the pull replication tooStefan Metzmacher1-0/+3
metze (This used to be commit 3383568c31545a6716eb7045b56d516d507c0b4d)
2007-10-10r12372: - make the periodic scheduling a bit easier, instead of passingStefan Metzmacher1-8/+0
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)
2007-10-10r12304: split out the wins partner configuration into a seperate ldb.Stefan Metzmacher1-0/+3
now $privatedir/wins_config.ldb contains the wins partners and $lockdir/wins.ldb contains the name records metze (This used to be commit baa4a7a9d4f16adf476846850a63dfbfd51b10b3)
2007-10-10r12242: - make the push notifications triggered by the change countStefan Metzmacher1-4/+15
- 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)
2007-10-10r12230: prepare for a generic periodic processing scheduling ofStefan Metzmacher1-0/+18
pull,push,scavenging and reread-config events metze (This used to be commit 977117278c4b9fc1b7845b6aa6d5862e5a776651)
2007-10-10r12200: - move the the winsreplication client and server code to the ↵Stefan Metzmacher1-19/+2
packet_context 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)
2007-10-10r11873: add some interval vars to the service contextStefan Metzmacher1-0/+28
metze (This used to be commit 1d80ba062ae8a0854e35eb8a3fdae56990b790b8)
2007-10-10r11547: - don't do pull replication when pullIntervall is 0Stefan Metzmacher1-0/+2
- don't do push replication when pushChangeCount is 0 metze (This used to be commit 4122e9ec3a4394738fa3c261dc92938ea86c3822)
2007-10-10r11052: bring samba4 uptodate with the samba4-winsrepl branch,Stefan Metzmacher1-0/+64
before the bad merge metze (This used to be commit 471c0ca4abb17fb5f73c0efed195c67628c1c06e)
2007-10-10r11043: r10362@SERNOX: metze | 2005-09-20 22:37:28 +0200Stefan Metzmacher1-0/+6
repare for pull replication support metze (This used to be commit a75402c45f5bcd3b199ad30af06ee34161c5560b)
2007-10-10r11032: r10342@SERNOX: metze | 2005-09-20 11:00:26 +0200Stefan Metzmacher1-7/+48
- 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)
2007-10-10r11023: r10310@SERNOX: metze | 2005-09-19 11:21:39 +0200Stefan Metzmacher1-0/+3
- open the winsdb in the wrepl server - add dummy function for setup the replication partners metze (This used to be commit da3d18e4545da3bd1841ffc31f253e533f7ea016)
2007-10-10r11014: r10139@SERNOX: metze | 2005-09-10 10:32:36 +0200Stefan Metzmacher1-0/+16
- 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)
2007-10-10r11007: r10109@SERNOX: metze | 2005-09-09 12:29:12 +0200Stefan Metzmacher1-0/+102
- 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)