Hi.

I have a web application, which uses data from database as well as local files 
(sort of CMS). I have (thanks to you and Jan Wieck) replication working, but 
I need also to sync some files between two servers at more or less the same 
point of time, when replication occurs to have on the slave machine a 
snapshot of database and app files from master host.

As I understood, launching 'subscribe set' replicates all changed tuples and 
begins to watch and replicate all subsequent changes, which occur in master 
db. This replication process can be stopped by launching 'unsubscribe set', 
right? So, I could launch every several hours something like this:

1. disable (at application level) master db modifications for a moment
2. start replication
3. rsync application files
4. stop replication
5. enable modifications of master db

But how can I determine the point of time in which the "initial" replication 
ends?

Richard.

-- 
"First they ignore you. Then they laugh at you. Then they
fight you. Then you win." - Mohandas Gandhi.