daitss/silo-pool — Issue #1: change where .lock files are maintained
Author: grf
Created: 2011-11-21 21:17:05+00:00
State: open

.lock files should not be written into the silo directories.
it forces all code to have write access to the silo even when it
doesn't need it; that constraint needs to be relaxed in several places
in the code. additionally, since the .lock files are often updated
long after the silo's been sealed, we end up having a lot of tape
thrashing. might also change tivoli to ignore .lock files on
restore, backup