Paul Wise wrote: > When I clone over SSH from another user's home directory, git-annex > writes the daemon.status outside of the git-annex I am cloning: > > pabs@chianamo ~/some/parent/directory $ git clone > server.example.com:~user/other/parent/directory/their-git-annex/ my-git-annex > Cloning into 'my-git-annex'... > remote: Counting objects: 331, done. > remote: Compressing objects: 100% (266/266), done. > remote: Total 331 (delta 65), reused 0 (delta 0) > Receiving objects: 100% (331/331), 28.37 KiB | 3.00 KiB/s, done. > Resolving deltas: 100% (65/65), done. > Checking connectivity... done. > pabs@chianamo ~/some/parent/directory $ cd my-git-annex/ > pabs@chianamo ~/some/parent/directory/my-git-annex (master=) $ git annex get > warning: Not setting branch master as its own upstream. > get IMG_1234.jpg (merging origin/git-annex into git-annex...) > (Recording state in git...) > (from origin...) > ... > > On my GNOME desktop I notice chianamo:~pabs/their-git-annex/ pop up: > > pabs@chianamo ~ $ find ~/their-git-annex/ > /home/pabs/their-git-annex/ > /home/pabs/their-git-annex/.git > /home/pabs/their-git-annex/.git/annex > /home/pabs/their-git-annex/.git/annex/daemon.status > pabs@chianamo ~ $ cat ~/their-git-annex/.git/annex/daemon.status > lastRunning:1410508665.453574s > scanComplete:True > sanityCheckRunning:False > lastSanityCheck:
daemon.status is only written if the git-annex assistant daemon is running, so there must be something to your configuration which you have not shown here. -- see shy jo
signature.asc
Description: Digital signature
