- Package:
- rtorrent
- Source:
- rtorrent
- Description:
- ncurses BitTorrent client based on LibTorrent from rakshasa
- Submitter:
- Jari Aalto
- Date:
- 2023-09-03 00:06:02 UTC
- Severity:
- normal
- Blocked By:
-
Bug Title 578598 4
Properly document the ratio.*= options minor stable testing unstable almost 5 years ago
537286 3
rtorrent: Example rtorrent.rc shows ratio command for version 0.8.3, not 0.8.4 minor stable testing unstable almost 5 years ago
630594 2
rtorrent: manpage out of date - ratio config has changed minor stable testing unstable almost 5 years ago
619207 6
rtorrent: enable_trackers=no/yes does not work in new version minor stable testing unstable almost 5 years ago
623727 3
command "cwd" does not exist minor stable testing unstable almost 5 years ago
537288 3
rtorrent: Example rtorrent.rc shows ratio command for version 0.8.3, not 0.8.4 minor stable testing unstable almost 5 years ago
620328 7
on_finished config option no longer recognized minor stable testing unstable almost 5 years ago
The manual page is quite good. It explains all the UI commands. But it lacks the information what the display indicators mean. Please add to the manual page complete content of these sections: "Main view windows" "Bottom line in GUI" from page: http://libtorrent.rakshasa.no/wiki/RTorrentUserGuide
Not only that, but the man page totally failes to mention the 'watch_directory' and 'untied_directory' directives for 'schedule'. They're right there in /usr/share/doc/rtorrent/examples/rtorrent.rc though. This lead to me thinking there was no way to get an already-running rtorrent instance to pick up a new torrent automatically, but there is. Please (get upstream to) update the man page! This is for Etch, but the man page for Lenny is no better.
retitle 483677 rtorrent: Incomplete and outdated documentation thanks The documentation of rtorrent is quite outdated. The manual page has not been updated in almost 3 years, and even then it was far from covering all the aspects of rtorrent. Since we have quite a bit of individual reports that boil down to documentation issues, I will use this bug to track them. What we'll need in the end is rtorrent(1) and rtorrent.rc(5) man pages, and a good example configuration file. Upstream knows about the problem [1] but lacks the time to tackle the issue themselves, so any help is more than welcome. [1] https://github.com/rakshasa/rtorrent/issues/24 Cheers,
Hello, Good morning, We have gone through your samples from a partner and Here is our Order List. Please do bear in mind that we are very much in need of this order, quote your competitive prices. Kindly send the Order confirmation. Your early reply will be much appreciated. Best Regards, Maryanah Erwin. PT FINDORA INTERNUSA Jln Pahlawan 66 Kec. Arjawinangun 45162 CIREBON West-Java INDONESIA tel : +62 231 357334 fax: +62 231 357260 email: marketing@findora.com
Hi, It seems the current man page (the one provided upstream along with the code source) still is outdated. i.e: `peer_exchange` isn't valid and has been replaced by protocol.pex I haven't checked thoroughly, but the community has written this: https://rtorrent-docs.readthedocs.io/en/latest/ and the Github wiki pages also contain some documentation. So I guess the man page is doomed.