[Tile-serving] osm2pgsql-replication?

[Lynn W. Deffenbaugh (Mr)]

Has anyone put a cron-safe wrapper around the new osm2pgsql-replication 
script for keeping a tile server's database current?

I'm migrating my old openstreetmap-tiles-update-expire implementation to 
use the new osm2pgsql-replication script, but am not sure exactly how to 
protect the latter from multiple cron invocations in the event that an 
update takes too long.

A second question is if anyone has a suitable --post-processing script 
that handles the incremental application of the dirty tiles list emitted 
by osm2pgsql.  My current setup uses render-expired, but it's all 
wrapped up in the single cron-safe script.

And a tertiary question is how to keep munin happy which is expecting a 
state.txt file containing the most recently updated timestamp for the 
calculation of the "Data import lag" graph.  I suspect this can be done 
with a suitable --post-processing script, but I'd be appreciative of any 
examples of this use.

And maybe a question that should have come first:  Is there any reason 
to switch away from a working openstreetmap-tiles-update-expire 
implementation?  Does osm2pgsql-replication have anything really good to 
offer?

Lynn (D)