On 9/24/2010 12:09 PM, Jeff Trawick wrote: > On Fri, Sep 24, 2010 at 12:50 PM, William A. Rowe Jr. <[email protected] > <mailto:[email protected]>> wrote: > > On 9/24/2010 11:12 AM, Rainer Jung wrote: > > > > I guess I'm also missing the bigger picture, but: > > > > - at first sight it sounds very reasonable to provide the > LD_LIBRARY_PATH as well > > > > - it might result in problems, if the binary to start uses system libs, > which exist in > > LD_LIBRARY_PATH and in system default locations in incompatible > versions. IMHO this is > > more a theoretical problem. E.g. the apr libs are versioned via the > soname such that the > > runtime linker won't link against a wrong version. > > But these same problems would be true at the shell, prior to invoking > httpd, no? > > > httpd could pick up library paths from the shell, but it could also pick up > paths from > bin/envvars; the latter is specifically tailored for dependencies > bundled+built with httpd > (and same ABI/debug-ability/etc.); for the slim cases where those defs are > not irrelevant > for the normal CGI/FastCGI, I dunno whether it would be good or bad more often
AIUI - apachectl triggers bin/envvars, which injects the appropriate LD_LIBRARY_PATH, yet this would still not be passed to child processes without my suggested commit, right? > This could be discussed purely in terms of features we already have: > > Do admins find 'SetEnv LD_LIBRARY_PATH foo' or 'PassEnv LD_LIBRARY_PATH' to > solve their > problem most often? > How often is it problematic to use 'PassEnv LD_LIBRARY_PATH'? Frequently enough to be a FAQ/documented? (And sometimes not well.) http://httpd.apache.org/docs/2.2/mod/mod_env.html#passenv The original mod_fcgid config docs (cannot find them anymore via google, even) http://httpd.apache.org/docs/2.2/mod/mod_cgi.html (whoops!) http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html (whoops!) http://bugs.php.net/bug.php?id=49173&edit=1 or as encountered 300k+ times in google; http://s.apache.org/cOb
