diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU <Adam@web> | 2013-11-05 11:10:15 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-11-05 11:10:15 +0000 |
| commit | 657ede36b4833ce6313346f3c624e71e3dc85cb0 (patch) | |
| tree | 71be5a547c2ad8fa670fb1bc361ec244ba2a1327 | |
| parent | 9fc588b73e5b001047f29d8d1ee83f88ce92cb89 (diff) | |
| -rw-r--r-- | doc/bugs/Transfers_continue_after_daemon_stopped.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bugs/Transfers_continue_after_daemon_stopped.mdwn b/doc/bugs/Transfers_continue_after_daemon_stopped.mdwn new file mode 100644 index 000000000..0d9b4f648 --- /dev/null +++ b/doc/bugs/Transfers_continue_after_daemon_stopped.mdwn @@ -0,0 +1,5 @@ +After creating a new pairing, I stopped the daemon through the webapp while it was syncing. The webapp shut down and was no longer accessible, but git-annex continued running in the background, along with git-annex-shell, and they continued to run new transfers with new rsync processes. This continued until I killed them all. + +I expected that when I stopped the daemon in the webapp, all git-annex processes and all transfers would stop. + +Using the 20131101 tarball. |