Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Chas Kissick
    @chkiss
    I'm also trying to set up a way to filter tagged torrents from most views, or better yet filter torrents out based on their tracker domain. I am really clueless here so feel free to just tell me you don't have time to help. Trying tagged first, I've tried "view.filter=main, tagged" but that seems to filter out everything - not just tagged/untagged torrents. Any support would be appreciated but I don't expect it obviously, seeing as I'm trying to customize it in a pretty specific way
    (it also returns a bunch of "Could not find '='." errors)
    PyroScope Project
    @pyroscope
    read teh docs on scripting. read them once more. understand(!) the numerous examples.
    trial + error does not work with an overcomplex thing like rt scripting.
    and intricate customization like you describe is just a lot of work
    ^q - read all the standard config files, then you'll know how to
    Chas Kissick
    @chkiss
    wow found it, and now I see it was right in front of my face in the docs the whole time
    thanks
    Snorre Selmer
    @SnorreSelmer
    How do I go about diagnosing why pyrotorque isn't "cron'ing"? I'm running this rTorrent/Flood Docker image (hub.docker.com/r/romancin/rutorrent-flood/), and I have gotten everything to work, except the queueing.
    I've added the PyroScope config to the rtorrent.rc, entered the path to the binaries, the watchdog is there, I've set up the torque.ini and tested it with 'pyrotorque --fg -v' and it works great..
    Just, I have to go into the container to kickstart the queue-processing
    PyroScope Project
    @pyroscope
    first thing is to check execute.log
    the watchdog is a rt schedule
    PyroScope Project
    @pyroscope
    executing a command, which might fail
    Snorre Selmer
    @SnorreSelmer
    Thanks! I can see from the log that the container tries to locate configs from /root/.pyroscope instead of from /config/.pyroscope. Somewhere there's a reference to "~/.pyroscope" and it's being run as root (which the container-creator insists is not ther case). I'll do some more diggin to see if I can find the culprit. Thanks for the help so far, now I just need to dig some more...
    DEBUG:pyrocore.scripts.pyrotorque.RtorrentQueueManager:Options: config_dir=None, config_file=[], cron=True, debug=False, defines=[], dry_run=False, guard_file=None, no_fork=False, pid_file=None, quiet=False, restart=False, status=False, stop=False, verbose=True
    DEBUG:pyrocore.util.load_config.ConfigLoader:Loading '/root/.pyroscope/config.ini'...
    WARNING:pyrocore.util.load_config.ConfigLoader:Configuration file '/root/.pyroscope/config.ini' not found, use the command 'pyroadmin --create-config' to create it!
    WARNING:pyrocore.util.load_config.ConfigLoader:Configuration file '/root/.pyroscope/config.py' not found!
    PyroScope Project
    @pyroscope
    well, home is home, and ~root is /root
    if you insist on non-standard paths, the easiest thing is a symlink
    i'd dump a container using root for runtime like a hot rotting potatoe
    Snorre Selmer
    @SnorreSelmer

    1: It's not me who made the container.
    2: I'm trying to fix this so it does.
    3: I totally agree, that's why I'm trying to fix this

    If I knew how to make this image myself, I'd try to do things differently. Like why does it have both Flood and ruTorrent? It's being "sold" as a Flood image..

    PyroScope Project
    @pyroscope
    well, DO use a symlink, no more ugly surprises
    PyroScope Project
    @pyroscope
    :mega: Debian Packages, as far as still supported, are now on GitHub
    https://github.com/pyroscope/rtorrent-ps/releases/tag/PS-1.1
    Specifically, Precise and Wheezy are gone
    BRTPOB
    @BRTPOB
    Hi, I'm trying to test out the rtorrent-ps docker image, but bintray is throwing a 403 when attempting to pull the packages down. Does anyone know of any workarounds for that?
    PyroScope Project
    @pyroscope
    git up and try again
    Gary Mann
    @moozhub
    anyone awake
    fatboysofatandaboy
    @fatboysofatandaboy
    hello. I have a few questions:
    1. does pimp-my-box support an easy method of deploying multiple rtorrent/rutorrent instances/users? context is I have around 4000 torrent files loaded, and have split them between multiple instances in the past to allow for easier management and to avoid rtorrent/rutorrent getting bogged down
    2. is the current stable build of rtorrent-ps protected against the dos vulnerability in rtorrent 0.9.6 (exploitdb 44894)? is there a focus on merging other security fixes from upstream rtorrent into rtorrent-ps?
    3. what client version does rtorrent-ps identify itself as to other clients? is it just "rtorrent/0.9.6/0.13.6" or does it specifically advertise "ps"?
      thanks
    saba sedigh
    @saba.sedigh_gitlab
    hello
    I am trying to install rtorrent-ps from the source
    issuing ./build.sh all give me this error:
    saba sedigh
    @saba.sedigh_gitlab
    admin/.local/rtorrent/0.9.6-PS-1.2-dev/lib/libcurl.so /home/admin/.local/rtorrent/0.9.6-PS-1.2-dev/lib/libtorrent.so -lxmlrpc_server -lxmlrpc -lxmlrpc_xmlparse -lxmlrpc_xmltok -lxmlrpc_util -lpthread -Wl,-rpath -Wl,/home/admin/.local/rtorrent/0.9.6-PS-1.2-dev/lib -Wl,-rpath -Wl,/home/admin/.local/rtorrent/0.9.6-PS-1.2-dev/lib
    /usr/bin/ld: display/libsub_display.a(window_file_list.o): in function `display::wstring_width(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int)':
    /home/admin/Downloads/rtorrent-ps/rtorrent-0.9.6/src/display/window_file_list.cc:72: undefined reference to `bool std::isprint<char>(char, std::locale const&)'
    collect2: error: ld returned 1 exit status
    gmake[3]: *** [Makefile:559: rtorrent] Error 1
    gmake[3]: Leaving directory '/home/admin/Downloads/rtorrent-ps/rtorrent-0.9.6/src'
    gmake[2]: *** [Makefile:630: all-recursive] Error 1
    gmake[2]: Leaving directory '/home/admin/Downloads/rtorrent-ps/rtorrent-0.9.6/src'
    gmake[1]: *** [Makefile:450: all-recursive] Error 1
    gmake[1]: Leaving directory '/home/admin/Downloads/rtorrent-ps/rtorrent-0.9.6'
    gmake: *** [Makefile:382: all] Error 2
    ```
    Do you have any idea of what is going on?
    PyroScope Project
    @pyroscope
    do we have any idea of the platform, gcc, et al?
    saba sedigh
    @saba.sedigh_gitlab
    linux ubuntu x86_64 version 21(hirsute)
    @pyroscope ^^
    gcc -v
    Using built-in specs.
    COLLECT_GCC=gcc
    COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper
    OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa
    OFFLOAD_TARGET_DEFAULT=1
    Target: x86_64-linux-gnu
    Configured with: ../src/configure -v --with-pkgversion='Ubuntu 10.3.0-1ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-10-gDeRY6/gcc-10-10.3.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-gDeRY6/gcc-10-10.3.0/debian/tmp-gcn/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-mutex
    Thread model: posix
    Supported LTO compression algorithms: zlib zstd
    gcc version 10.3.0 (Ubuntu 10.3.0-ubuntu1)
    PyroScope Project
    @pyroscope
    install docker and use the docker build
    or try the LTS prebuilt package
    or add hirsute whereever focal appears in build.sh
    i do not support non-lts OOTB
    PyroScope Project
    @pyroscope
    use a current docker and git head of rt-ps and docker_deb works
    saba sedigh
    @saba.sedigh_gitlab
    @pyroscope I see. but running from the source should build the rt-ps in whatever system you want.
    Does the error I provided produce any clues.
    I don't need support for this version of ubuntu but just some help figuring out what went wrong...
    thank you
    PyroScope Project
    @pyroscope
    not using gcc10 for starters
    and i do not debug other people's build envs
    that is why there's the dockerfiles
    Chris Hills
    @Chaz6
    Building with GCC 9 works fine, does not work with GCC 11, so I guess stick to 9