diff options
| -rw-r--r-- | doc/bugs/git-annex_on_NAS_eats_all_memory/comment_6_2ad3d0960929533fef8f827bbf06f085._comment | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_6_2ad3d0960929533fef8f827bbf06f085._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_6_2ad3d0960929533fef8f827bbf06f085._comment new file mode 100644 index 000000000..01900e69f --- /dev/null +++ b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_6_2ad3d0960929533fef8f827bbf06f085._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2015-02-12T18:20:39Z" + content=""" +Does it work if ssh allocates a pseudo-tty? + +ssh -t myuser@mynas "git-annex-shell 'configlist' 'mygitannexfolder'" + +There must be some fundamental difference in the environment between the +same command being run over ssh and at the console that is making it behave +differently one way than the other. It could be the pseudo-tty, or an +environment variable, or a different user account, or whatever. + +I think that the only way to get to the bottom of this problem is going to be +finding out what the difference is. (Or perhaps stracing it to see what +it's doing when it uses so much memory.) +"""]] |