Sean Sprague wrote: > Rod! > >>> 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. > > I run 32-bit, and tested my theorem by setting my default lib path > through crle to the 64-bit path, and hosed the box predictably to the > extent that I had to boot from CD and mop up the pieces ;-) Been there > many times before with crle, and enjoyed every minute of the > self-induced stress :-)
I'm happy for you're enjoyment, but perhaps things could have been easier: root 12. crle -c /var/ld/ld.config -l /oh/what/a/mess root 13. date ld.so.1: ls: fatal: libc.so.1: open failed: No such file or directory Killed root 14. LD_NOCONFIG=yes rm /var/ld/ld.config root 15. date Tue May 27 14:21:35 PDT 2008 Better yet, create your ld.config in a temporary location, use LD_CONFIG_32 to point to it, then install it in the default location when you're happy with the results. Yes, lots of rope. -- Rod.
