"env" variable problem? [ Solved ]

[sunburnt]

Hi amigo; That`s what I`m doing for AppDir, but AppLib is different.
It contains all the shared libs. for the AppDir apps.
It`s just adding a few more variables to the config. file to have AppDir.
There can be many AppDir dirs. for apps., but only one AppLib so far.

I renamed APP_DIR to AppDir as the ROX-Filer uses $APP_DIR.

Reading the config. file for each app. start isn`t so bad. But not good...


# I`m still trying to find a "one method fits all" for no-install apps.
The chroot idea is interesting, but I`m a little confused on how to do it.

[Flash]

"The beautiful thing about standards is that there so many to choose from."

[jpeps]

APP_DIR is not a 'proprietary' enivronmental variable.

It doesn't work from /etc/init.d. Unsetting it first doesn't work either. There's no problem using it as a local variable.

edit: I got it to work by getting out of my user shell into root. Interestingly, my unset command also only works from root shell. If running from root, the unset command isn't even needed.

[sunburnt]

jamesbond found it...

ROX-Filer sets: APP_DIR='' when it`s started.

So in the ROX desktop env APP_DIR gets trashed.

[jpeps]

So in the ROX desktop env APP_DIR gets trashed.

May be one example of the dangers of running in /root.

[sunburnt]

I`m not sure how being root affects this.

Root or not, Rox will set the variable, so it probably doesn`t matter.

But there may be other considerations I haven`t accounted for.

[jpeps]

I`m not sure how being root affects this.

Root or not, Rox will set the variable, so it probably doesn`t matter.

But there may be other considerations I haven`t accounted for.

Sure, in the case of /init.d/, if the variable doesn't work I could always choose to use it anyway, or more generally, I can always attempt to force something when an obvious conflict arises.