comments

2 files changed, 32 insertions, 0 deletions

diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_4_3b226c7ce28f1caee2d5e568d91c96bc._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_4_3b226c7ce28f1caee2d5e568d91c96bc._comment
new file mode 100644
index 000000000..dc9c1ce1b
--- /dev/null
+++ b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_4_3b226c7ce28f1caee2d5e568d91c96bc._comment
@@ -0,0 +1,24 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2015-02-11T16:48:58Z"
+ content="""
+You seem to have catted /proc/pid/cmdline, so the parameters are all
+mashed together without the separating `\0` being visible. Not the best way
+to examine a process. Use `ps`.
+
+It may be that the --library-path parameter is too long and is being
+truncated. That's what appears to be the case when it ends at
+"/shimmed/git-annex-shell/git-annex-shell-c".
+
+However, Linux's command-line length limits are much much longer than this
+command line, so it shouldn't be truncated. And, I don't know why it would
+only be truncated when the script is called by ssh.
+
+I suggest that you edit `git-annex.linux/git-annex-shell`  and
+`git-annex.linux/runshell` and `git-annex.linux/bin/git-annex-shell` ; make
+the first line of each shell script be "#!/bin/sh -x".
+
+Then you can try running it again via ssh and on the NAS, and paste the
+debug output.
+"""]]
diff --git a/doc/tips/Synology_NAS_and_git_annex/comment_6_954fc1b423208928fafdeb8cdac47c50._comment b/doc/tips/Synology_NAS_and_git_annex/comment_6_954fc1b423208928fafdeb8cdac47c50._comment
new file mode 100644
index 000000000..b9d037bd1
--- /dev/null
+++ b/doc/tips/Synology_NAS_and_git_annex/comment_6_954fc1b423208928fafdeb8cdac47c50._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 6"""
+ date="2015-02-11T17:05:15Z"
+ content="""
+There's a bug report for the memory use hang now: 
+[[bugs/git-annex_on_NAS_eats_all_memory]]
+"""]]