Mailing List Archive: Issue 1384 in cherokee: Inherit Environment

Status: New
Owner: ----

New issue 1384 by daniel.n...@gmail.com: Inherit Environment
http://code.google.com/p/cherokee/issues/detail?id=1384

What steps will reproduce the problem?
1. Start Cherokee-Admin
2. Go to page "Source" and "PHP Interpreter"
3. See "Inherit Environment"

What is the expected output? What do you see instead?
I see:
Inherit Environment is not ticked (that's by default). The description
says "Whether the new child process should inherit the environment
variables from the server process. Default: yes."

So there is no way to deactivate that option because when it's ticked, it's
enabled and when it's not ticked, it's still enabled because the
description says yes?

What version of the product are you using? On what operating system?
Linux euve3638 2.6.32-028stab094.3 #1 SMP Thu Sep 22 12:47:37 MSD 2011
x86_64 GNU/Linux

Latest Cherokeefrom Github

Please provide any additional information below.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Updates:
Status: WontFix
Labels: Type-Enhancement Component-Admin Usability

Comment #1 on issue 1384 by ste...@konink.de: Inherit Environment
http://code.google.com/p/cherokee/issues/detail?id=1384

No, when a new information source is made manually, or some configuration
voodoo is done to leave out the option completely cherokee will initialise
the variable with "true". You can infact untick it and get the expected
results. This type of writing is done across the admin interface, so I
can't see a way how we can change that to a unambigious interpretation.

Please, if the disable option doesn't work, obviously we would like to hear
it.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev