Closed GoogleCodeExporter closed 9 years ago
This can all be done :
1. Lock the settings down : in script.js , look for Show("stg");and make that
//Show("stg"); (around line 2268)
2. Set up multiple rtorrent.rc's , all with there own settings
3. .htpassword your apache folders
Original comment by rascal...@gmail.com
on 13 Aug 2009 at 4:31
This can't be realized in scheme "Multiple users->one rTorrent". Because
rTorrent
can't manage two or more torrents with some hash, for example. You need to
configure
one rTorrent (and ruTorrent) copy per one user.
Original comment by novik65
on 13 Aug 2009 at 7:34
I understand novik65, byt that's not what I was interested in.
Sorry if I made my point a bit unclear, I decided to give rutorrent a try after
using
wtorrent because it was in inactive development.
I'm interested in the user management wtorrent has, a login page, add users to
access
rutorrent and their specified download directory.
Original comment by chris.za...@gmail.com
on 13 Aug 2009 at 8:41
You mean - all users will share common torrent's list? And have previlegies to
start/stop any torrents?
Original comment by novik65
on 13 Aug 2009 at 9:54
Original comment by novik65
on 18 Aug 2009 at 11:21
Having an option to allow users to see the whole torrent list and to control
others
torrents would be the difference of being an "admin" and a "user".
Original comment by chris.za...@gmail.com
on 18 Aug 2009 at 11:28
In that case see comment 2. For example, you is a simple user of such system.
And can
see & manage own torrents only. Next, you try to add file some.torrent. But
another
user of this system ALREADY downloaded this file. It seeding. But you can't see
it.
rTorrent can't store 2 torrents with some hash, and it can't download file
some.torrent. As result you see nothing - rTorrent hasn't API for retrieve
errors
about unsuccessful torrent's addition. What we will do with this?
Original comment by novik65
on 18 Aug 2009 at 11:49
Ahh, I see what you mean now. My proposition then is to allow users to view the
whole
file list but only control their own torrents until such time that rutorrent
does
have an api to retrieve such errors in the future. If I am asking of too much
then
please stop me.
Original comment by chris.za...@gmail.com
on 18 Aug 2009 at 11:57
Really this must be a separate project, because it requires too match changes in
code. And now i can't see a good way to implement all of its. May be in future.
Original comment by novik65
on 18 Aug 2009 at 12:08
in all honestly running multiple copies of rtorrent doesn't add much load at
all. I
did an experiment this week.
on a core2 duo machine with 4 gb ram i set up a single rtorrent and ran a bunch
of
torrents, started with 5, then added 5 more, kept doing this till i got to 40
torrents. The load seemed to only go up a fraction, and only when torrents got
fast,
and it didn't seem to matter how many torrents i ran, just how fast they were
running. I then did the same thing, only with 6 copies of rtorrent running,
and the
load wasn't really more than a fraction higher....forinstance right now, i'm
running
14 copies of rtorrent with speeds on the server between 10-30 MB/s (not Mbit/s,
MByte/s) and the load is 0.35 right now.
With this many copies of rtorrent running, the load never goes over 0.7 and
gets as
low as 0.06
OF COURSE this IS freebsd....which is VASTLY less load than something like
ubuntu
Original comment by Wonslung@gmail.com
on 18 Aug 2009 at 5:08
Original comment by novik65
on 19 Aug 2009 at 4:30
I would like a way to just add torrents for some users, and only admin users
can stop, pause, slow down, etc. the torrents. The basic users either upload a
torrent via the web GUI, an FTP folder, or something like dropbox. Once that
upload starts they can access a common downloads folder. All users have read
access to this, not write or delete. I will run a cron to either move or delete
the files automatically after one week.
Would this be difficult to change or implement? Would .htaccess or .htpasswd be
all I need? If so, how hard would it be to create a plugin to manage the
.htaccess and .htpasswd files?
Original comment by spaz...@gmail.com
on 29 Jan 2011 at 4:35
well you should be able to easily add torrents using a watch directory (or
allow it) or with the auto-watch plugin
i think rutorrent has support for disabling options for a user via the
access.ini though i'm not entirely sure if you can do everything you are
talking about....this would be better asked about in the forums at
http://forums.rutorrent.org
Original comment by Wonslung@gmail.com
on 29 Jan 2011 at 6:06
Original issue reported on code.google.com by
chris.za...@gmail.com
on 12 Aug 2009 at 11:31