1. Those are not the same as what is in SuperPoussin's kit. New 32 bit utorrents require the new glibc which is a problem. The ones I pointed to are 64 bit builds that happen to use the older libraries and don't require the new glibc.
2. I couldn't find the SSL libraries built anywhere. I'm not sure what the legality is of me distributing them built already.
3. No you don't need to do the glibc update. I think that would be dangerous. Hopefully you didn't get very far
4. The Web UI for utorrent is at: http://<yourhostip>/gui.
From the shell interface lets see if you have all the libraries right:
cd /usr/local/utorrent
ldd utserver
My ldd outputs this:
warehouse6:/usr/local/utorrent# ldd utserver
linux-vdso.so.1 => (0x00007fff241ff000)
libssl.so.0.9.8 => /lib64/libssl.so.0.9.8 (0x00007f6418f54000)
libcrypto.so.0.9.8 => /lib64/libcrypto.so.0.9.8 (0x00007f6418bc4000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f64189a8000)
libm.so.6 => /lib64/libm.so.6 (0x00007f6418723000)
librt.so.1 => /lib64/librt.so.1 (0x00007f641851a000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f64192ab000)
libc.so.6 => /lib64/libc.so.6 (0x00007f64181a9000)
/lib64/ld-linux-x86-64.so.2 (0x00007f64191a6000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f6417fa5000)
If all the libraries are not resolved then utorrent won't run. If they are all found then let's see if utserver is running:
ps -ef | grep utserver
Mine outputs
warehouse6:/usr/local/utorrent# ps -ef | grep utserver
root 7809 7454 0 23:19 pts/1 00:00:00 grep utserver
nobody 8238 1 0 06:25 ? 00:00:31 /usr/local/utorrent/utserver -logfile /c/addons-config/utorrent/utorrent.log -configfile /c/addons-config/utorrent/utserver.conf
If your system doesn't have the process running then lets run it manually just to see if it starts. So just type:
./utserver
What output do you get?
steve
