I been trying to get the utorrent working with a socket, as long as I can remeber..
Tried ubuntu/centos/slack/fedora/debian
Tried lighttp/apache/cherokee...
Tried repos, tried compiling...
After almost a month yesterday I tried with arch, their wiki about wtorrent was great, which worked for rutorrent too. Yet the moment I switched to local socket it all died...
So I decided to do try the same tutorial with centos, something I'm more familiar with. And after 9 hours, I come to realize the sanity is overrated.
At first the Arch wiki guide failed, so I found "http://forums.rutorrent.org/index.php?topic=161.0". It was a centos guide, written in 2010, what could go wrong? First the the lighttp was changed. A lot. The /etc/lighttpd/lighttpd.conf, was "include"d a modules conf, and all of the modules had their own conf files in an subfolder. After trying to uncomment the modules.conf for an half our I came to realize that the real uncommenting was down below. After adding stuff to the fastcgi.conf and scgi.conf, I went on to the next step. Phpinfo was working, I added the dag's repo, a trusted packager. Than the writer asked to install a rpms from "fateyev.com". Having no idea who the hell is fateyev, I found it was a some russian site. I decided to compile from source, after few tricks rtorrent worked. Rutorrent failed to connect to rtorrent, something I'm more than familiar with.
Defeated one more time by the rutorrent I betrayed the CLI, and hoped cherokee-admin GUI will make things easier for me. Well, there was no rtorrent wizard anymore. I thought maybe EPEL repository deleted rtorrent wizard for legal concerns so compiled the cherokee from source. Still no wizard, I did a grep to source code to find it was still there, but not visible in GUI. I tried to remove everything else, copy rtorrent wizard under the moodle wizard and overwrite the rtorret.py of the wizard to worpress.py. Still nothing. After spending another hour on editing to source code; I went back to the good old apache. mod_scgi give me some hard time on centos but I got it installed. And here I'm...full of questions.
Some of the tutorials I tried :
http://code.google.com/p/rutorrent/wiki/Installation
http://www.facebook.com/note.php?note_id=385534226615&_fb_noscript=1
http://forums.rutorrent.org/index.php?topic=161.0
http://filesharefreak.com/2010/02/13/how-to-install-rtorrent-rutorrent-using-socket-ssl-authentication-on-ubuntu-or-debian/
http://www.torrent-invites.com/tutorials/23981-ubuntu-rtorrent-wtorrent-rutorrent-tutorial.html
http://wiki.archlinux.org/index.php/WTorrent
http://wiki.archlinux.org/index.php/RTorrent
http://libtorrent.rakshasa.no/wiki/RTorrentXMLRPCGuide
First I'm in an openVZ container, is this causing some kind of physical limitation to me?
Today I heard somebody implying it was impossible to get local socket working in centos, does this true?
How can I add /tmp/rpc.socket to the apache config like "SCGIMount /RPC2 127.0.0.1:5000" ?
What is the rpc plugin?
I been seeing too many localhost:5000 tutorials but this sounds as unsecure as it gets. Its like keeping the door open and hope people won't steal something. Is there something I'm missing?
Tried ubuntu/centos/slack/fedora/debian
Tried lighttp/apache/cherokee...
Tried repos, tried compiling...
After almost a month yesterday I tried with arch, their wiki about wtorrent was great, which worked for rutorrent too. Yet the moment I switched to local socket it all died...
So I decided to do try the same tutorial with centos, something I'm more familiar with. And after 9 hours, I come to realize the sanity is overrated.
At first the Arch wiki guide failed, so I found "http://forums.rutorrent.org/index.php?topic=161.0". It was a centos guide, written in 2010, what could go wrong? First the the lighttp was changed. A lot. The /etc/lighttpd/lighttpd.conf, was "include"d a modules conf, and all of the modules had their own conf files in an subfolder. After trying to uncomment the modules.conf for an half our I came to realize that the real uncommenting was down below. After adding stuff to the fastcgi.conf and scgi.conf, I went on to the next step. Phpinfo was working, I added the dag's repo, a trusted packager. Than the writer asked to install a rpms from "fateyev.com". Having no idea who the hell is fateyev, I found it was a some russian site. I decided to compile from source, after few tricks rtorrent worked. Rutorrent failed to connect to rtorrent, something I'm more than familiar with.
Defeated one more time by the rutorrent I betrayed the CLI, and hoped cherokee-admin GUI will make things easier for me. Well, there was no rtorrent wizard anymore. I thought maybe EPEL repository deleted rtorrent wizard for legal concerns so compiled the cherokee from source. Still no wizard, I did a grep to source code to find it was still there, but not visible in GUI. I tried to remove everything else, copy rtorrent wizard under the moodle wizard and overwrite the rtorret.py of the wizard to worpress.py. Still nothing. After spending another hour on editing to source code; I went back to the good old apache. mod_scgi give me some hard time on centos but I got it installed. And here I'm...full of questions.
Some of the tutorials I tried :
http://code.google.com/p/rutorrent/wiki/Installation
http://www.facebook.com/note.php?note_id=385534226615&_fb_noscript=1
http://forums.rutorrent.org/index.php?topic=161.0
http://filesharefreak.com/2010/02/13/how-to-install-rtorrent-rutorrent-using-socket-ssl-authentication-on-ubuntu-or-debian/
http://www.torrent-invites.com/tutorials/23981-ubuntu-rtorrent-wtorrent-rutorrent-tutorial.html
http://wiki.archlinux.org/index.php/WTorrent
http://wiki.archlinux.org/index.php/RTorrent
http://libtorrent.rakshasa.no/wiki/RTorrentXMLRPCGuide
First I'm in an openVZ container, is this causing some kind of physical limitation to me?
Today I heard somebody implying it was impossible to get local socket working in centos, does this true?
How can I add /tmp/rpc.socket to the apache config like "SCGIMount /RPC2 127.0.0.1:5000" ?
What is the rpc plugin?
I been seeing too many localhost:5000 tutorials but this sounds as unsecure as it gets. Its like keeping the door open and hope people won't steal something. Is there something I'm missing?