From 43426b18000633d3fe227ba2aefaac4779efdaf0 Mon Sep 17 00:00:00 2001 From: hannes Date: Sun, 8 Jul 2012 10:18:32 +0000 Subject: --- ...nc_remote_is_not_available_from_a_cloned_repo.mdwn | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn (limited to 'doc') diff --git a/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn b/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn new file mode 100644 index 000000000..e3d642844 --- /dev/null +++ b/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn @@ -0,0 +1,19 @@ +I have a git annex repository, and a sync to a remote rsync server (with shared encryption), named "rsync". + +When I clone the repository, I thought it would work as described for S3 (http://git-annex.branchable.com/tips/using_Amazon_S3/): + +> $ git annex initremote rsync + +> git-annex: Specify the type of remote with type= + +When I run + +> $ git initremote rsync type=rsync rsyncurl=ssh.example.com:/myrsync encryption=shared + +I get a git remote -- but the data available on the rsync server is not accessible locally + +> $ git whereis + +> git-annex: whereis: 19631 failed + +The original is a git annex from cabal, the cloned repository uses 3.20120522. -- cgit v1.2.3 From ce96276c0a5d9f98c57b52dbca93d130139979a5 Mon Sep 17 00:00:00 2001 From: hannes Date: Sun, 8 Jul 2012 11:57:28 +0000 Subject: --- doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn b/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn index e3d642844..9d48e2100 100644 --- a/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn +++ b/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn @@ -16,4 +16,4 @@ I get a git remote -- but the data available on the rsync server is not accessib > git-annex: whereis: 19631 failed -The original is a git annex from cabal, the cloned repository uses 3.20120522. +The original is a git annex 3.20120629, the cloned repository uses 3.20120522. -- cgit v1.2.3 From 252f12f3c81dd222d1e1794c9e2a0318a819b292 Mon Sep 17 00:00:00 2001 From: hannes Date: Sun, 8 Jul 2012 13:24:30 +0000 Subject: removed --- ...nc_remote_is_not_available_from_a_cloned_repo.mdwn | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn (limited to 'doc') diff --git a/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn b/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn deleted file mode 100644 index 9d48e2100..000000000 --- a/doc/forum/rsync_remote_is_not_available_from_a_cloned_repo.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -I have a git annex repository, and a sync to a remote rsync server (with shared encryption), named "rsync". - -When I clone the repository, I thought it would work as described for S3 (http://git-annex.branchable.com/tips/using_Amazon_S3/): - -> $ git annex initremote rsync - -> git-annex: Specify the type of remote with type= - -When I run - -> $ git initremote rsync type=rsync rsyncurl=ssh.example.com:/myrsync encryption=shared - -I get a git remote -- but the data available on the rsync server is not accessible locally - -> $ git whereis - -> git-annex: whereis: 19631 failed - -The original is a git annex 3.20120629, the cloned repository uses 3.20120522. -- cgit v1.2.3 From b71191df8d025ad22bc5692af3461ae3d3fa96b3 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sun, 8 Jul 2012 18:13:58 +0000 Subject: Added a comment --- .../comment_4_c25a8eb369e546f65e1a72d89f43066f._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/Issue_on_OSX_with_some_system_limits/comment_4_c25a8eb369e546f65e1a72d89f43066f._comment (limited to 'doc') diff --git a/doc/bugs/Issue_on_OSX_with_some_system_limits/comment_4_c25a8eb369e546f65e1a72d89f43066f._comment b/doc/bugs/Issue_on_OSX_with_some_system_limits/comment_4_c25a8eb369e546f65e1a72d89f43066f._comment new file mode 100644 index 000000000..509752bf1 --- /dev/null +++ b/doc/bugs/Issue_on_OSX_with_some_system_limits/comment_4_c25a8eb369e546f65e1a72d89f43066f._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + subject="comment 4" + date="2012-07-08T18:13:58Z" + content=""" +On kFreeBSD, I get this: + + $ sysctl kern.maxfilesperproc + kern.maxfilesperproc: 11095 + +But ulimit still has 1024 limit, so you'd need to adjust both, as root. Messy.. +"""]] -- cgit v1.2.3