Re: Env var on the fly



On Sat, Sep 29, 2007 at 08:23:59AM -0700, Francesco Pietra wrote:
Having defined (in my .bashrc) the environmental variables for computing suites
X and Y (PATH to them) it happens - because of some bug in X - that on running
certain programs of Y, executables of X are called (and of course not found).

If I undefine the env var X, all programs of Y run perfectly.

Is any simple way to define the env var X on the fly, when X is needed, without
having to use X as another user? (which would overcomplicate the matter because
there is an scp link from the computing machine to and from a desktop, where I
am).

export X="blah"

or do you need it to happen automatically? in which case your
application needs to do this.

A

Attachment: signature.asc
Description: Digital signature



Relevant Pages

  • Re: ZIP bug
    ... Is this a known bug that has been fixed in a more recent ... like to avoid a situation where I'm unable to decompress an existing ... 32-bit executables? ... With or without encryption? ...
    (comp.os.os2.bugs)
  • Re: glibc backward compatibility
    ... There are 2 executables in the picture: ... For that kind of dependency, the loader will search all globally ... There is no bug: ...
    (comp.os.linux.development.system)
  • Re: Showstopping FreeBSD 6.1 bug
    ... I need to report a serious bug in 6.1-RELEASE. ... sysinstall appears to work correctly but fails to install a kernel ... target filesystem. ... cannotfind any executables (it can, however, find executables ...
    (freebsd-questions)
  • Re: newbiedoc error [Re: Testing URIs not working]
    ... > You should report that as a bug. ... you should file a bug against newbiedoc. ... Executables ...
    (Debian-User)