On Jan 16, 08 23:52:26 +0200, Zvi Har'El wrote:
> Hi
>
>
> Thanks, but no thanks. I am not interested in tricks to set
> LD_LIBRARY_PATH. This is not what the screen mailing list about.
>
>
> I am concerned about the fact that screen removes LD_LIBRARY_PATH from the
> environment, and I believe t
Yes. just "sudo chmod u-s /usr/local/bin/screen-4.0.3" did it!!!1 I am
grateful.
On 17/01/08 00:43, Zvi Har'El wrote:
I think you pinpointed the problem. I have on my RHEL4 machine two
installation of screen. An older one, which comes with the system, in
/usr/bin/screen:
~$ ls -l /usr/bin/s
I think you pinpointed the problem. I have on my RHEL4 machine two
installation of screen. An older one, which comes with the system, in
/usr/bin/screen:
~$ ls -l /usr/bin/screen
-rwxr-xr-x 1 root root 324440 2004-09-11 12:10 /usr/bin/screen
~$ /usr/bin/screen --version
Screen version 4.00.02 (
On Wed, 16 Jan 2008, Zvi Har'El wrote:
Hi
Thanks, but no thanks. I am not interested in tricks to set
LD_LIBRARY_PATH. This is not what the screen mailing list about.
I am concerned about the fact that screen removes LD_LIBRARY_PATH from
the environment, and I believe this behavior is a bug
Trying to get things less hazy.
From ld.so(8):
The necessary shared libraries needed by the program are searched for
in the following order
o Using the environment variable LD_LIBRARY_PATH
(LD_AOUT_LIBRARY_PATH for a.out programs). Exc
My memory is hazy, but I believe I tracked this down to glibc doing this
on behalf of screen because it's a setgid binary.
Details are hazy because this was a year or three ago.
.laz
Zvi Har'El ([EMAIL PROTECTED]) said:
> Hi
>
>
> Thanks, but no thanks. I am not interested in tricks to set
>
Hi
Thanks, but no thanks. I am not interested in tricks to set
LD_LIBRARY_PATH. This is not what the screen mailing list about.
I am concerned about the fact that screen removes LD_LIBRARY_PATH from
the environment, and I believe this behavior is a bug.
Zvi.
On 16/01/08 23:15, Randy Be
When you first login Bash will read /etc/bash.bashrc and also
$HOME/.bashrc to set stuff like your path($PATH) and other environment
variables. Always put your LD_LIBRARY_PATH exports in either of these
two files. New bash screen sessions will always read /etc/bash.bashrc
and also $HOME/.bashrc on
Of course this works. But the problem is that LD_LIBRARY_PATH is part of
the configuration of the run (shared libraries used in addition to the
standard libraries). Of course I can write a script to edit .bashrc, but
this is a ridiculed solution. Why cannot screen export the original
LD_LIBRARY
Try putting the LD_LIBRARY_PATH in your .bashrc, that should work.
On Jan 16, 2008 11:59 AM, Zvi Har'El <[EMAIL PROTECTED]> wrote:
> I am using screen to run several applications simultaneously in the
> same environment. The environment preparation consists of exporting
> various variables, in
I am using screen to run several applications simultaneously in the
same environment. The environment preparation consists of exporting
various variables, including LD_LIBRARY_PATH. However, after running
screen, the various windows show the original environment (of course
few changes,
11 matches
Mail list logo
