'File not found' error on known existing files?
 

Something I'm not understanding here about the meaning of the 'file not found' error as pertains to uploads...

Example: When I switch to the Monitor tab, I can see a number of attempts to get a particular file 'foo.mp3' from my shares. A number of users attempts will have a 'file not found' error in the Status column, while another user may be happily downloading 'foo.mp3'. Why are so many users getting 'file not found' errors for files that are clearly visible and available to other users?

I did a forum search on this, and I came across one comment that stated (paraphrased) "file not found errors on the monitor tab are the result of the anti-freeloading feature denying file access to freeloading users".

If this is true, why is an ambiguous error like 'file not found' being used to indicate a freeloader rejection (why not 'rejected')? And if not, what is causing this odd behaviour?

Thanks, sorry if this is a redundant question.

You can chage these activites if you are not happy with them. Go to Tools > Options. Go to the Advanced tab. One th bottom part of the window, there is a small section called "Connection Preferencing." If you have 1 or higher in the input field AND/OR have your Allow Freeloaders slider at Rarely, then your uploads will be unsuccessful to varying degrees.

I would really recommend making sure that your settings are active so as to preserve the existing integrity of the network. If people who don't share files (freeloaders) are taking up all of your bandwidth, someone who is actually sharing files will not be able to get anything from you. People who actually contribute to the network's content should have the first priority. :-)

Ok, I'll take it that the comment I read was more or less correct.

In this case, what are the suggested settings (to maintain network integrity) for the 'number of files' and 'allow freeloaders' slider?

And why is the error message so misleading (or in the least, uninformative)? :)

I don't know why this particular error has such an odd name. Maybe, it's to fool the downloader that the *file is missing* instead of saying *no freeloading allowed*. :-)

I would say to keep your file number at 1 or higher. I'm mean, and so I say you have to be sharing 25 or more files. For any new person using Gnutella, this might sound harsh, but I'm sure you can dig out the Napster downlaods and share them. ;-) Also, I have the slider on "rarely" to make sure freeloaders don't take my upload slots and bandwidth.

Anyone else have any different/better settings to use?

You think 200 is mean?!??!?!?!?! I set it at 500 (I share way more than that) specifically because I want priority access to go to folks with broadband and other serious users. Not to be mean to modem users... file number is a bad measure anyway. Gigabytes shared would be a much more usefull criterion. Most of my many many files are over 10MB... and many are closer to 1GB. I don't want some punk on a 14.4 trying to download something that will take a month when there are other folks that can utilize my bandwidth better.

The thing is, though, there's nothing really preventing anyone (even modem users or people with small HDDs) from just grabbing 10,000 5kB gifs off a newsgroup.

Besides, it's a multivariable decision. I have broadband but a relatively slow computer. For me this means I can get and share big files readily, but my machine cannot handle having more than just a few people grabbing files at a time. Modem users shouldn't tie up slots on T3's or T1's... those are for Cable and DSL. Modem users should connect to the Cable and DSL users... but more importantly to eachother. That's how you foster a healthy network.

Oh, and don't forget. "Rarely" doesn't mean zero. It means ten (percent, I think). Even with my strict 500 minimum, my upload slots are always full... ...and almost exclusively by folks downloading at broadband speeds. So I guess I'm doing something right.

So what's wrong with saying *no freeloading allowed* ? Slap 'em in the face a few times and maybe they'll get the message!

I set the maximum simultaneous connections per user to 1. I see users downloading a 200 MB file at 3.5 KB/s and asking for a second file. Get a clue people! It'll take 16 hours to download one file and you want to take two of my upload slots? I don't think so! High speed users aren't much better. Even at 12.5 KB/s it'll take 4.5 hours to download the file. Asking for a second file increases your time to 9 hours and increases the chances that you'll end up with two partial files instead of one complete one. Don't be greedy.

Another trick I use is when I want to wind up my session, if people are downloading from me I won't cut them off, I just set the number of connections to zero. Existing downloads continue, but new attempts are denied.

Ed

freeloading
 

On the Cnet download page, they have an opinion survey, and one Limewire user stated a problem that exists in the system is that you can set your files setting to 200, but the person on the other end can HAVE 200 files but puts his upload to zero, so he is still freeloading. He has the files, but no one can access them. Hopefully future versions will come up with a workable solution. I also set my uploads to zero just before I'm ready to log off, to give the existing people a chance to finish, while not adding anyone new. Great way to go.