aMule Forum
English => aMule Help => Topic started by: slystone on October 31, 2008, 12:51:48 PM
-
Hi,
I'm using amuled.
when files are removed from the download directory are they also automatically removed from the share? Or have I to force resharing? If yes, how is possibile this operation with amuled? I don't want to restar it.
I tried to get this info looking into the source code, but I was not able to find this information by myself.
Tank you very much,
slY
-
when files are removed from the download directory are they also automatically removed from the share?
Yes
-
No. Only when someone starts downloading that file from you.
-
No. Only when someone starts downloading that file from you.
So, remove files from the download folder is a bad option or not?
I don't want users to stay in queue waiting for a file that no longer exists.
It's not polite :)
-
It is a bad option. You can reload your shares with an amulecmd command, I'm pretty sure. Just open amulecmd and type "help".
-
It is a bad option. You can reload your shares with an amulecmd command, I'm pretty sure. Just open amulecmd and type "help".
You are right!
The command is"reload shared"
I did't saw it :D
Tank you very much!
-
as i could see, amule remove a file from shared-list when it can't read it (file not found for example).
but anyway it got an error first...
best way is to reload shared (with amulecmd).
-
No. Only when someone starts downloading that file from you.
Which, in my world is equivalent to "yes". Any P2P system is "best effort", not "guaranteed service". So, it doesn't matter (statistically) when (at which point in time) file being removed from queue.
-
A small bug I obseverd on amuled/amuleweb 2.2.2: when removing a shared file through amuleweb while someone is downloading it, amuleweb seems to crash almost every time.
@slystone: does this happen in your setup as well?
-
@slystone: does this happen in your setup as well?
No, for now I've not noticed it, I rarely use the web interface, and much more rarely for remove files. I should try it.
-
No. Only when someone starts downloading that file from you.
Which, in my world is equivalent to "yes". Any P2P system is "best effort", not "guaranteed service". So, it doesn't matter (statistically) when (at which point in time) file being removed from queue.
Publication of files to servers/kad that are not there is bad. It happens, there is no sensible solution for us other than tell the user that is better to reload shareds. But removing it from the folder will NOT remove it from shared files UNLESS someone asks for it AND reaches the top of the queue, as explained before. That's what he asked, and your answer was incomplete, if not wrong.
-
All this very interesting and 100% correct. Let's see whether it have any effect in real life.
Take a look on those events:
* File is removed from shared
* User reach top of queue
Those events are 1) uncorrelated and 2) relatively rare. Given this, probability of "user reaches top of queue but file not there" doesn't change whether you reload file or not. See Poisson distribution. http://en.wikipedia.org/wiki/Poisson_distribution (http://en.wikipedia.org/wiki/Poisson_distribution)
-
Poisson distributions don't apply here, sorry.
The situation reminds me of Schrödingers cat (http://en.wikipedia.org/wiki/Schrodingers_cat).
-
Poisson distributions don't apply here, sorry.
Why? Because you say so? How about doing your homework before posting?
Publication of files to servers/kad that are not there is bad.
Yes, but effect is minimal unless significant %% of your files are "not there". This would make "fake server".
And it affects all users searching such file.
You assume that once you hit "reload", all KAD nodes are instantly updated. They are not.
-
Poisson distributions don't apply here, sorry.
The situation reminds me of Schrödingers cat (http://en.wikipedia.org/wiki/Schrodingers_cat).
And this reminds me of Chewbacca defense. Since Poisson distribution have nothing to do with Schrödingers cat. Do you any idea what "Schrödingers cat" is?
-
Are you seriously suggesting a Poisson distribution claiming that the event of a file not being in the disk anymore and the event of someone reaching the top of the queue FOR THAT FILE, WHICH IS NOT THERE, are not correlated?
Have you done your homework before posting?
-
[Do you any idea what "Schrödingers cat" is?
No, I'm just practicing random ranting. :-*
-
Are you seriously suggesting a Poisson distribution claiming that the event of a file not being in the disk anymore and the event of someone reaching the top of the queue FOR THAT FILE, WHICH IS NOT THERE, are not correlated?
Have you done your homework before posting?
Oh, I did my homework on this very specific topic plenty of times.
Let's put some formalities.
There's no event "file not in disk anymore". There IS event "I checked if file is there and result is false". Despite being similar, this is not the same.
One of ways to describe Poisson distribution is time you spend on bus station before bus arrives. You CAN choose WHEN to come to station, but this WILL not change distribution of T(t) - time spent in waiting. This relies on assumption that event "bus come to station" and "you come to station" are RARE in INDEPENDENT.
Same thing here. You have following events:
a. File deleted from disk
b. Share reloaded
c. Client enters queue
d. Client reach top of queue but file is not there.
The claim is that correlation between P(b) and P(c) is very small, because P(a), P(b) are both small. Moreover, once Corr{P(d|c),P(b)}=0 since share reloading doesn't affect clients already in queue.
Now, let's also consider the fact, that (d) => (b) (share automatically reloaded once some client hit top of queue). So, you have MANY clients; but it's enough that only ONE hit top of queue to reload shares. This means that F(b|c) -> 1 and it doesn't matter very match whether you hit "reload" manually or not.