This is with Jaunty, and I think the effect I'm seeing is a known "feature" of ssh-agent being set GID. glibc will strip certain sensitive environment variables.
The funny thing is.. this was working for a while, but I can't figure out what changed. Either the env-var stripping wasn't working, or my system wasn't running the desktop as a sub-process of ssh-agent.
For now, I've worked around my issue by adding my local gEDA testing install folder to /etc/ld.so.conf.d, although that wouldn't work well if I wasn't "root" as well as pcjc2.
As an alternative.. would it be possible to run ~/.profile from a subprocess of ssh-agent as well? (Or to re-set the LD_LIBRARY_PATH on the sub-process run by ssh-agent?)
Sorry, I did indeed mean 2009.. time does fly!
This is with Jaunty, and I think the effect I'm seeing is a known "feature" of ssh-agent being set GID. glibc will strip certain sensitive environment variables.
The funny thing is.. this was working for a while, but I can't figure out what changed. Either the env-var stripping wasn't working, or my system wasn't running the desktop as a sub-process of ssh-agent.
For now, I've worked around my issue by adding my local gEDA testing install folder to /etc/ld.so.conf.d, although that wouldn't work well if I wasn't "root" as well as pcjc2.
As an alternative.. would it be possible to run ~/.profile from a subprocess of ssh-agent as well? (Or to re-set the LD_LIBRARY_PATH on the sub-process run by ssh-agent?)