Re: Ktorrent problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 11/22/2016 04:35 PM, geo.inbox.ignored wrote:

On 11/22/2016 04:02 PM, jd1008 wrote:

On 11/22/2016 05:45 AM, geo.inbox.ignored wrote:
On 11/20/2016 03:06 PM, jd1008 wrote:
FYI.

Quiting ktorrent does not cause ktorrent to exit.
After I quit, I run ps -ef | grep ktorrent
and it is still running long after I quit.

hi jd.

it has been years when last ran a torrent download. do not recall about
problems in terminating, other than someone was pulling from me.


are you sure all operations are finished?
how do you have 'configure shutdown' set?
are any 'events' still running?
any plugins still running?
are you running log files?


think about running 'wireshark', or some other analyzer to watch traffic.

running 'kde system monitor' and watching 'system load' is an easy way
to see ups/downs'. 'process table' will show you when it actually
stops running, select 'memory' and 'own processes'.


Well, I don't know.
When I ask ktorrent to quit, it OUGHT to mean cease and desist (i.e.
stop) all operations.
If that is NOT what it does, then it is a flaw.

maybe yes, maybe no. maybe ktorrent is written to finish any active
operations before program closes. such as, some 1, 2, or 3 others are
pulling from you.

if you totally shut down on some, anyone pulling from you has to find
another site to pull. such would increase total time for other user.

concept of torrent is to find a _close_ site to pull from, thereby
decreasing pull time.

example. you need a 5GB file that is at a far off remote site that
is only available over 10 hops and each hop is at 10MB.

via torrent, there are 20 sites, where each is 4 hops at 600MB.

which would you rather pull from?

what is going to happen if 5 of those sites shut down on you?

one of the torrent programs i have used showed, by default, the various
sites i was connected to, speed, bytes pulled. during the pull, sites
would drop out and be replaced, speed would go up and down. i found it
interesting to watch. not important, but interesting.

torrent is all about sharing the load and gaining speed.


Sorry to say you are making too many assertions not supported by actual facts.
maybe this or maybe  that just does not cut it.
a torrent client must be coded to terminate downloads and uploads when the quite is executed. Otherwise, the user is deceived into thinking that his network bandwidth will now
be more available for other network activity.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]
  Powered by Linux