On 3/7/06, Chris 'Xenon' Hanson <[EMAIL PROTECTED]> wrote: > yary wrote: > > Pardon me for giving what may be a naive answer, but how about putting > > /usr/local/lib into the LD_LIBRARY_PATH env variable before starting > > the wanrouter script? > > It's an obvious answer, but I figured there must be a good reason > (security?) that > /usr/local/lib _isn't_ in the LD_LIBRARY_PATH at that stage, and it didn't > seem like a > good idea for an installer to tamper with the system's LD_LIBRARY_PATH. > Partly I'm looking > for insight as to why it is the way it is currently.
I can see it being a security thing, but you only have to set that environment variable for the subshell that's starting the wanrouter, not for the whole system at that stage of boot. This seems to work for /bin/sh: $ (export fff=rrr && echo $fff) rrr $ echo $fff $ You have to trust /usr/local enough to run the port/package in the first place... so try launching wanrouter with "(export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib && /bin/bash /usr/local/bin/wanrouter)" - your startup script will add the local libs to its search path but the rest of that bootup stage won't. And if that's incorrect someone will surely point out the error of my ways! -y
