You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Scott McPeak <sm...@cs.berkeley.edu> on 2001/11/18 04:11:09 UTC

mod_env/8792: SetEnv does not set PATH (PR 370)

>Number:         8792
>Category:       mod_env
>Synopsis:       SetEnv does not set PATH (PR 370)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Nov 17 19:20:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     smcpeak@cs.berkeley.edu
>Release:        1.3.22
>Organization:
apache
>Environment:
linux 2.4, gcc 2.95.3
>Description:
As documented in PR 370, SetEnv doesn't set the PATH variable.  I would have liked
to simply add this note to PR 370, but your interface has no way to do that.

I think this bug should be fixed.  It was first reported in 1997.  It is annoying
to have to recompile apache, or else hack the (several) scripts which possibly
start apache, just to set a decent default path.  I want my apache configuration
to be as self-contained as possible, so (e.g.) I can move it to another machine
without having to remember to hack this or that system script.

<rant>
If the apache team does not want to fix this, can it at least be documented
in mod_env's docs *which* environment variables have this problem?  It's very
annoying to spend 30 minutes of trial and error, and then web searching, only
to discover this is a known problem which no one bothered to document.
</rant>
>How-To-Repeat:
Compile with mod_env (in by default) and say

  SetEnv PATH /usr/local/bin:/bin:/usr/bin
>Fix:
Either make it take effect, or else print to the logs that it is being ignored,
and document that with mod_env.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]