aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-02-16 19:36:26 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-02-16 19:36:26 -0400
commit4b67ae596a133d285cc28593e26c47e5b14720c3 (patch)
treea9e9a81cf6f1b9a99db57a50cdcf8ff5a5df178c /doc/bugs
parenta7b290e6fa07fc17cdbd058cdaac98bb3f82294f (diff)
Linux standalone: Improved process names of linker shimmed programs.
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/weird_entry_in_process_list.mdwn2
-rw-r--r--doc/bugs/weird_entry_in_process_list/comment_1_61e1fc604b49964ef97f31c9d5546afc._comment13
2 files changed, 15 insertions, 0 deletions
diff --git a/doc/bugs/weird_entry_in_process_list.mdwn b/doc/bugs/weird_entry_in_process_list.mdwn
index e09ad8140..4efa3f8d8 100644
--- a/doc/bugs/weird_entry_in_process_list.mdwn
+++ b/doc/bugs/weird_entry_in_process_list.mdwn
@@ -37,3 +37,5 @@ root@koumbit-mp-test:/var/isuma/media/video# ps axf | grep annex
"""]]
couldn't it alter its process name to make this a little more intuitive? This is especially problematic because i am trying to hook git-annex into Puppet and Facter, which require me to guess where the various git-annex repos are on the server. The way i was doing that so far was with `lsof -c 'git-annex' -F0tn`, which is obviously failing under those circumstances.... Unless there's a better way to find those repos across the system? I assume there's a git-annex assistant running here... --[[anarcat]]
+
+> [[fixed|done]] --[[Joey]]
diff --git a/doc/bugs/weird_entry_in_process_list/comment_1_61e1fc604b49964ef97f31c9d5546afc._comment b/doc/bugs/weird_entry_in_process_list/comment_1_61e1fc604b49964ef97f31c9d5546afc._comment
new file mode 100644
index 000000000..95fe6cf79
--- /dev/null
+++ b/doc/bugs/weird_entry_in_process_list/comment_1_61e1fc604b49964ef97f31c9d5546afc._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-02-16T23:35:08Z"
+ content="""
+Haskell programs actually cannot alter their process name. I've had a bug
+open on ghc for a year about that.
+
+However, I can make a nicer symlink name than ld-linux.so, and use that,
+and it will then be clear what program is being run, although the
+parameters to it will still be unusual due to the shimming used in the
+standalone build.
+"""]]