step 1: metaserver

The first step into improving csync2 is having a metadata server. Actually the only problem with csync2 is the metadata management. The locking and such. It hurts. So how does that look like:

The processes:

csi: csync2 inetd service

This one handles incoming connections. It's intended only to receive files.

csc: csync2 hint checker

This one parses al hints, and turns them into dirties, or not.

csh: csync2 hint insert.

Dumb inserting of hints.

csu: csync2 updates to external servers, handles the dirty queues

Topic revision: r5 - 02 Nov 2011 - 13:10:56 - TWikiGuest
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback