On 06/26/2016 05:24 PM, Abrolag wrote: > I'm steadily more inclined to think a time based solution would be most > reliable. If the time entry is always being updated by the instance holding > the > lock (even if it's only on an hourly basis) anything more than a couple of > hours old must be an ophaned one.
Most of the time I run into lock files being an irritation, it's due to a crash, and I'll be trying again very shortly thereafter. If it has to wait an hour to be orphaned, that isn't going to do developers any good. -- D. Michael McIntyre ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Rosegarden-user mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
