C. Michael Pilato wrote: >> On 05/31/2013 10:35 AM, Julian Foad wrote: >>> Just an opinion from general experience in the world of computers. With >>> any system where some resource is reserved (locked), it can be useful to >>> find out who/what has the lock. So, a system that tells me the repo is >>> currently locked by which of the following: >>> >>> commit >>> pack >>> freeze >>> ... >>> >>> would be useful, in my opinion. An output that enumerates one of the >>> above list would be useful. >> >> Don't most OSes provide tooling for this, though? > > Just to clarify, I'm talking about the likes of this: > > $ cd ~/tests > $ flock lockfile lsof | grep `pwd`/lockfile > flock 2912 cmpilato 4uW REG 8,5 0 3500312 > /home/cmpilato/tests/lockfile
That's OK for manual investigation, but we're looking for a solution that suitable for building into infrastructure management scripts, so it needs to be portable and reliable, and stable across OS upgrades and the like. See Philip's original introduction to this email thread: > One of my colleagues at WANdisco asked some questions about using > freeze. The first thing he wanted to know is how to detect whether a > freeze is running. There are various approaches: look at running > processes, look at processes with the lock file open, implement some > external lock, etc. but none are reliable or portable. The only > reliable way to do it is for Subversion to provide some sort of > implementation. (Wording tweak: I'd say "none are reliable *and* portable".) - Julian
