Re: envvar's leaking into open()

Chet Ramey wrote: [EMAIL PROTECTED] wrote: hello, i made some observation by chance. bash 3.2 seems to leak environment variables into open() syscalls (older bash 2.0 does not show this behaviour) Bash isn't doing the opens -- they're coming from the libc locale code. Bash isn

Re: envvar's leaking into open()

[EMAIL PROTECTED] wrote: > hello, > > i made some observation by chance. > > bash 3.2 seems to leak environment variables into open() syscalls (older bash > 2.0 does not show this behaviour) Bash isn't doing the opens -- they're coming from the libc locale code. -- ``The lyf so short, the c

Re: envvar's leaking into open()

uot; LC_MESSAGES="POSIX" LC_PAPER="POSIX" LC_NAME="POSIX" LC_ADDRESS="POSIX" LC_TELEPHONE="POSIX" LC_MEASUREMENT="POSIX" LC_IDENTIFICATION="POSIX" LC_ALL= > -Ursprüngliche Nachricht- > Von: <[EMAIL PROTECTED]>

envvar's leaking into open()

hello, i made some observation by chance. bash 3.2 seems to leak environment variables into open() syscalls (older bash 2.0 does not show this behaviour) this may not be an issue here or do not any harm - but at least opening such non-existing files is nonsense and it really looks like a bug