Hosed my SSH
Hosed ssh on my slicehost.com
1. installed openssl when it was ALREADY THERE
2. accidentally deleted libcrypt.a (on hardy) in an attempt to delete libcrypto.a
3. the make install installed openssl to /usr/local/lib and now ssh was looking there first instead of /usr/lib. It threw some error about not recognizing the version and ssh wouldn’t start
Great help from slicehost. They even sent me their own copy of libcrypt.a. I ended up doing a few sudo apt-get remove openssh-server. Don’t know if that did anything.
/etc/init.d/ssh start (or reload) with no problems after removing the files from /usr/local/lib
I’ll use apt-get from now on.
I think i understand how the openssl libs work now. If you do a `locate libcrypto.so` it shows you that it’s in /usr/lib. I think that whatever you put in /usr/local/lib overrides what’s in /usr/lib. For some reason the tclink build.sh was looking only in /usr/local/lib and so i put a symlink to the /usr/lib instead of trying to download and compile my own openssl libs.
Then I copied the tclink.so library in to /usr/lib/ruby/1.6/x86_64-linux so all the Ruby can use it.
