[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: path handling changes to try out ...
From: |
Dan Pascu |
Subject: |
Re: path handling changes to try out ... |
Date: |
Fri, 15 Feb 2002 01:47:24 +0200 (EET) |
On 15 Feb, Helge Hess wrote:
> On Freitag, Februar 15, 2002, at 12:21 Uhr, Dan Pascu wrote:
>> You surely can, but it obviously can not apply to the program that was
>> just started, because that is only used when loading dynlibs at startup.
>> But it will apply to any child started from there on, by the app that
>> set LD_LIBRARY_PATH.
>
> What about bundles loaded after the initial startup ? Will they use a
> modified LD_LIBRARY_PATH ?
if they are started as kids of the process that modified the
environment var. (or a child of some child...). which I guess it's the
case, because they all originate from an initial command you launched.
I mean the bundle is started by some fork/exec from the original
command you launched.
>
> Anyway, since it isn't really possible for an executable to
> "autoconfigure", this might be the justification for the
> executable.template in case of a missing setup ? (I think Nicola wanted
> to remove support for that ..)
>
> Greetings
> Helge
--
Dan