Pull in changes automatically from somewhere to decrease lock chances

[marcel@…]

Another idea perhaps to decrease locking problems?

Many trac+monotone installs probably use a cron like solution to pull revisions from a database which is used by a group of people to push to. That is, one push.db to which developers normally push their changes and a mtntrac.db which is used by the plugin in trac.

At times this causes cron errors because the db is locked. Would it be possible to have the mtn plugin pull changes in from somewhere configurable, at a configurable interval to reduce lock problems?

[Thomas Moschny]

For the plugin being able to initiate a pull it'd need to drop the automate stdio connection, because pull is currently not among the commands available for automate (which should be added anyway).

On IRC, Nathaniel suggested a ​proxying daemon. This isn't a bad idea, and I might implement that as a helper for TracMonotone.