On Nov 19, 1:44 am, Jani Tiainen <[EMAIL PROTECTED]> wrote: > You don't need to develop fancy. Just make pre-commit-hook to lock your > backup script and post-commit-hook to release it. and you're done. > > Now you have made your backups as atomic too.
Alas, this just reduces the window where an inconsistency could happen, as the post-commit script itself does not start atomically. This means that there will be a span of time where the backup can start and the post-commit hasn't started yet or has not gotten far enough to lock out backups. As I am managing a system with many heavily used projects, these statistically unlikely timing events show up quite regularly on our hourly backups (which use hotcopy), but not on our nightly backups (which shut down the server). What is really needed is a way to have Trac itself perform the ticket update when it next observes that a commit has happened (and includes ticket info in the message). My current problem is that it looks like Trac is not yet extensible enough to handle this as a plugin. Instead, it appears that I would have to patch each implementation of the version control API. - Justin R. Cutler --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
