On Sat, Mar 29, 2003 at 02:13:24PM -0600, Rich Smrcina wrote: > It is the java executable that comes with WAS. It invokes the installer to > install Java, IBM HTTP Server and WAS. > > Here is the directory entry for it: > -r-xr-xr-x 1 root root 1955 2001-12-18 14:10 java
It is a shell script. Moreever, I would expect it to play some games with your environment, including LD_LIBRARY_PATH . Normally this shouldn't matter for something as basic as glibc (libc version 6), as it is generally loaded from the ld.so 's cache. But just in case, could you post here the contents of /etc/ld.so.conf ? When was it last changed? (any chance that running ldconfig changes things?) Those are shots in the dark, "just in case". An alternative way to debug shell scripts: sh -x /path/to/java This would give you a trace of what commands the script is running, and values are set to variables. pipes look a bit weird there, though. Also: On Saturday 29 March 2003 11:56 am, Mark Post wrote: > Richard, > > It may be expecting a slightly older version of whatever version of glibc > you're running. If you figure out just what binary is trying to use > these libraries, do an "ldd -v" command against it, and you'll get more > specific > > information as to just what it's looking for: > ldd -v bootshell I'm not sure. libstdc++ has an ever-changing ABI, and is anything but backward-compatible. But glibc is backward compatible. The "compat" package doesn't have an older glibc, right? What exactly are those programs that fail? Are they the system copies or are they local copies that come with the package? (I expect the trace above to help with it). If they are the system copies, and ld.so.conf has sane values, -- Tzafrir Cohen +---------------------------+ http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend| mailto:[EMAIL PROTECTED] +---------------------------+
