open_issues/translator_environment_variables: New.

1 files changed, 31 insertions, 0 deletions

diff --git a/open_issues/translator_environment_variables.mdwn b/open_issues/translator_environment_variables.mdwn
new file mode 100644
index 00000000..cae5a494
--- /dev/null
+++ b/open_issues/translator_environment_variables.mdwn
@@ -0,0 +1,31 @@
+[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!tag open_issue_hurd]]
+
+IRC, unknown channel, unknown date.
+
+    <cfhammar> BTW, is settrans -a supposed to clear all env variables?
+    <cfhammar> or can I consider it a bug ;-)
+    <cfhammar> scolobb: yeah, seems the problem is in libfshelp
+    <scolobb> cfhammar: Are you talking about fshelp_start_translator_long?
+    <scolobb> (I can remember that it does something to the environment indeed)
+    <cfhammar> scolobb: yes, I think it's the culprit
+    <cfhammar> clearing the environment makes sense for passive translators I guess, but not active ones
+    <scolobb> Hm, searching ``env'' in hurd/libfshelp/start-translator-long.c gives me nothing :-(
+    <scolobb> I think the problem might be in the fact that fshelp_start_translator_long just doesn't copy the environment, but I may be wrong.
+    <cfhammar> scolobb: yeah, that's my guess also
+    <scolobb> Well, I don't know proc, but there might be a way to copy the environment to a task when you know its ID, what do you think?
+    <scolobb> I can see proc_set_arg_locations in process.defs, which sees to set something connected with environment, but I'm not sure whether it suits your needs.
+    <cfhammar> scolobb: it seems that the env isn't passed to file_exec in fshelp_start_translator_long
+    <scolobb> cfhammar: Yeah, that's right
+    <scolobb> I wonder what could the motivation for not passing the environment to a child process
+    <cfhammar> hmm... fshelp_start_translator_long parameterizes everything except env...
+    <cfhammar> perhaps there needs to be a fshelp_start_translator_longer ;-)