File-Rsync-Mirror-Recent
    
    
  
  
  
view release on metacpan or search on metacpan
	By upping the flag often one can easily ruin the slaves.
	last out of band change? dirtymark?
	Anyway, this implies that we read a potentially existing recentfile
	before we write one.
	And it implies that we have an eventloop that keeps us busy in 2-3
	cycles, one for current stuff (tight loop) and one for the recentfiles
	(cascade when principal has changed), one for the old stuff after a
	dirtymark change.
	And it implies that the out-of-band change in any of the recentfiles
	must have a lock on the principal file and there is the place to set the
	dirtymark.
	* start a FAQ, especially quick start guide questions. Also to aid those
	problematic areas where we have no good solution, like the "links"
	option to rsync.
( run in 0.475 second using v1.01-cache-2.11-cpan-c333fce770f )