| commit | 18a86d1b253d90285ea3364497ed71a62167f68f | |
| author | Kyle J. McKay <mackyle@gmail.com> | |
| Mon, 15 Sep 2014 00:11:39 +0000 (14 17:11 -0700) | ||
| committer | Kyle J. McKay <mackyle@gmail.com> | |
| Mon, 15 Sep 2014 00:11:39 +0000 (14 17:11 -0700) | ||
| tree | 633b2fd5884e5edf972d7eaabaa303900447df9b | treesnapshot (tar.gz zip) |
| parent | 3ca76e5400ab85f8bda57dd7d4c13723eec7cd28 | commitdiff |
gc.sh: attempt to recover from a stale gc.pid.lock file
Under normal conditions a gc.pid.lock file should exist
only briefly for much less than a second. On the other
hand, if failures occur (i.e. disk full) the gc.pid.lock
file can end up being left around. Attempt to recover
from this situation when the gc.pid.lock file is stale
(i.e. over 1 hour old) by removing it and then sleeping
for a brief period to compensate for the possible race
condition between testing for staleness and then removing
that stale file.
Under normal conditions a gc.pid.lock file should exist
only briefly for much less than a second. On the other
hand, if failures occur (i.e. disk full) the gc.pid.lock
file can end up being left around. Attempt to recover
from this situation when the gc.pid.lock file is stale
(i.e. over 1 hour old) by removing it and then sleeping
for a brief period to compensate for the possible race
condition between testing for staleness and then removing
that stale file.
| jobd/gc.sh | diffblobblamehistory |