Sean Sprague wrote: > This is just a guess, but I suspect that you are running a 64-bit > kernel, and that by setting the default lib path, you are breaking > isaexec, and a such, ps and its ilk will fail. I have never ever liked > crle in the slightest, but you could try: > > crle -c /var/ld/ld.config -l /lib/64:/usr/lib/64 > > I could be waaaay off though...
The above would probably kill every 32-bit process :-) crle(1) does provide copious amounts of rope to hang yourself. There are two default configuration file locations: /var/ld/ld.config and /var/ld/64/ld.config the latter being manipulated with crle's -64 option. The idea is to use each to specify information relevant to the individual ELF class. Note, you can mix information, like search paths. Folks have, and continue to specify 32-bit and 64-bit search paths in one LD_LIBRARY_PATH setting for example. ld.so.1 will dutifully load any file found in a path that matches the necessary dependency. ld.so.1 will reject, and move on to the next search path, any object that is the wrong class. However, this loading, validation and unloading costs. It is therefore recommended that you use the appropriate variables only for the correct class (note for every LD_XXX variable there's an LD_XXX_32 and LD_XXX_64 equivalent). Of course, you really shouldn't use LD_LIBRARY_PATH at all. Runpaths that incorporate $ORIGIN should be all you need: http://blogs.sun.com/rie/entry/tt_ld_library_path_tt -- Rod.
