On Mar 6, 2012, at 17:28 29, James Harrison wrote: > Nothing was decided on, afaik (other than "It's damn difficult!").
Not particularly difficult, but it does require some inter-host notification infrastructure that we don't have as yet so as to allow stale locks to be broken (otherwise you risk being semi-permanently locked out of logs that are being edited on hosts that go offline unexpectedly). I do plan to implement this in the next major version of Rivendell. I foresee two modes operation (settable on a per-service basis): 1) Strict -- Don't allow concurrent editing of logs at all. 2) Permissive -- Warn the user when about to open a log that is already open elsewhere, but allow them to override the warning. Any other use cases we need to consider? Cheers! |-------------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-------------------------------------------------------------------------| | Do not try to think outside of the box. That's impossible. Instead, | | realise the truth. There is no box. | | --Quoted by "larsmjoh" on GrokLaw.net | |-------------------------------------------------------------------------| _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
