Results 1 to 8 of 8

Thread: rtorrent with rutorrent frontend through optware

  1. #1
    Join Date
    Jul 2011
    Posts
    27

    Default rtorrent with rutorrent frontend through optware

    I've been trying to install rtorrent on the javelin through the optware repository. I prefer rtorrent to transmission as rtorrent will actually allow you to move around and rename files in a torrent.

    Best I can tell rtorrent installed successfully. It seems functional going through the CLI, but that's a hassle for normal use. I installed another instance of lighttpd and have it running on a separate port so it doesn't interfere with the javelin's own instance of lighttpd. I have this setup working on my router, so I was able to copy all the config files. The problem I run into is when I try to use rutorrent as a web frontend. I get a nice seg fault from rtorrent every time I try to launch the web interface. I was wondering if you guys had any suggestions?

  2. #2
    Join Date
    Jul 2011
    Posts
    27

    Default

    Here is a screen shot of the seg fault that I get.

    segfault.jpg

  3. #3
    Join Date
    Mar 2012
    Location
    NYC, NY
    Posts
    89

    Default

    libtorrent.so is not playing nice with the kernel that the javelin is compiled with.
    try running /promise/lib/ldconfig to see if it complains about a certain module, if the module exist in both opt folder and somewhere else in the javelin, delete/rename the copy from the opt folder, and run ldconfig again until it comes back clean, that should take care of your error.
    Last edited by ruben00; 05-10-2012 at 03:46 PM.

  4. #4
    Join Date
    Jul 2011
    Posts
    27

    Default

    I was able to clean things up so /promise/lib/ldconfig runs without complaining and taking offline the raid array, but I'm still getting the same error when I go to launch rutorrent once rtorrent is running. There are no files names the same in both /lib and /opt/lib. Any other ideas?

  5. #5
    Join Date
    Mar 2012
    Location
    NYC, NY
    Posts
    89

    Default

    hmmm, the ldconfig was my only card, sorry, how about another rtorrent front end, does it give you the same error?

  6. #6
    Join Date
    Jul 2011
    Posts
    27

    Default

    I was able to get wtorrent to work as a frontend, but it's not ideal as it doesn't support the same feature set as rutorrent and is quite limited in comparison. I noticed that rutorrent complains about not being able to access the stat program and id program. I was reading that the id program that's installed on the Javelin may not be compliant as it does not support the -G flag. Looking at my rutorrent setup on my router, I can see that that one does support -G. Where might I be able to get new versions of those programs?

  7. #7
    Join Date
    Mar 2012
    Location
    NYC, NY
    Posts
    89

    Default

    whats the ID program (the name fo the binary i mean)? and if you run rutorrent front end from your router, can you point it to the rtorrent client on the javelin?

  8. #8
    Join Date
    Jul 2011
    Posts
    27

    Default

    The id program is supposed to be part of the coreutils package. It is supposed to print real and effective user and group IDs. I haven't had much luck getting the router frontend to work with the NAS backend, but I haven't put as much effort into it as I probably could. I may end up revisiting that approach.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •