From 61e96d7be4106223691886a0882cd6ea8c2944a5 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Tue, 28 Jul 2020 15:18:44 +0000 Subject: [PATCH] Added a comment --- ..._20db4ecf9debcc2662ec69a6ad9b37c6._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/todo/may_be___40__again__41___to_prelink_or_somehow_avoid_all_the_failing_opens__63__/comment_10_20db4ecf9debcc2662ec69a6ad9b37c6._comment diff --git a/doc/todo/may_be___40__again__41___to_prelink_or_somehow_avoid_all_the_failing_opens__63__/comment_10_20db4ecf9debcc2662ec69a6ad9b37c6._comment b/doc/todo/may_be___40__again__41___to_prelink_or_somehow_avoid_all_the_failing_opens__63__/comment_10_20db4ecf9debcc2662ec69a6ad9b37c6._comment new file mode 100644 index 0000000000..2522a8f7a0 --- /dev/null +++ b/doc/todo/may_be___40__again__41___to_prelink_or_somehow_avoid_all_the_failing_opens__63__/comment_10_20db4ecf9debcc2662ec69a6ad9b37c6._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 10" + date="2020-07-28T15:18:40Z" + content=""" +WOW -- a random discovery and possible note to myself: I am getting all those libpcre misses when I run `git annex version` within a git repository and not otherwise: + +``` +$> strace -f git-annex version 2>&1 | awk '/libpcre.*so.*/{print}' | nl | tail -n 1 + 1 [pid 3702554] openat(AT_FDCWD, \"/lib/x86_64-linux-gnu/libpcre.so.3\", O_RDONLY|O_CLOEXEC) = 3 + +$> mkdir repo; cd repo; git init +Initialized empty Git repository in /tmp/repo/.git/ + +$> strace -f git-annex version 2>&1 | awk '/libpcre.*so.*/{print}' | nl | tail -n 1 + 41 [pid 3702907] openat(AT_FDCWD, \"/usr/lib/git-annex.linux//usr/lib/x86_64-linux-gnu/libpcre2-8.so.0\", O_RDONLY|O_CLOEXEC) = 3 +``` + +Not sure why `git annex version` needs to run `git` when inside a git repo for its `version`. (same happens for `git annex --help`) +"""]]