Improve shutdown due to --time-limit, especially for fsck

* Perform a clean shutdown when --time-limit is reached.
  This includes running queued git commands, and cleanup actions normally
  run when a command is finished.
* fsck: Commit incremental fsck database when --time-limit is reached.
  Previously, some of the last files fscked did not make it into the
  database when using --time-limit.

Note that this changes Annex.addCleanup hooks, to run after --time-limit
expires. Fsck was using such a hook to clean up after a
--incremental-schedule, and that shouldn't run when --time-limit exipires
it. So, instead, moved that cleanup code to be run by cleanupIncremental.
Resulted in some data type juggling.
This commit is contained in:
Joey Hess 2015-07-31 16:00:13 -04:00
parent c0b598b7f1
commit 9dfe03dbcd
7 changed files with 89 additions and 47 deletions

11
debian/changelog vendored
View file

@ -1,3 +1,14 @@
git-annex (5.20150732) UNRELEASED; urgency=medium
* Perform a clean shutdown when --time-limit is reached.
This includes running queued git commands, and cleanup actions normally
run when a command is finished.
* fsck: Commit incremental fsck database when --time-limit is reached.
Previously, some of the last files fscked did not make it into the
database when using --time-limit.
-- Joey Hess <id@joeyh.name> Fri, 31 Jul 2015 12:31:39 -0400
git-annex (5.20150731) unstable; urgency=medium
* webapp: Support enabling known gitlab.com remotes.