Got a Question? Email the question and I'll try to answer it.
Q. Why run a Bazooka GWC?
A. To help out the Gnutella2 network, thats why! By running a cache, you help Gnutella2 users discover other Gnutella2 users and more users equals more value to the network.
Q. How much bandwidth will my cache use?
A. This will vary on use and how much data is sent out for every request to the cache. Lets assume our cache gets 150,000 hits a day. Each GET request will be approximately 1500 Bytes or 1.5 KBs. So ((150 000 X 1500) / 100 000) = 225 MB a day or 6750 MB (6.7GB) a month.
Depending on the use of the cache, you will see at least 5GB data being transmitted per month. One of the Gnutella2 cache's I run gets about 400 000 hits per day and utilises at least 18GB a month.
Q. That seems like a lot of bandwidth, why run a Bazooka GWC again?
A. The more Cache's we have to spread the load - the less bandwidth each cache will use. Then again, sometimes you have misbehaving clients that eat GWCs up, Bazooka 0.3.5b has a feature to limit client requests from particular clients and versions.
Q. How do I use KickStart?
A. In your baz_settings.php file, change the value of $BAZ_KS_ON to 1. E.g. $BAZ_KS_ON = 1;
You also need the URL of an already working cache, it doesnt have to be a Bazooka cache.
In your browser, navigate to Bazooka to activate the KickStart module like so:
A. All caches are checked against current lists if they are sent to a cache via an UPDATE request. If caches are found to be invalid or not found, then the cache will be placed in a retry system.
Good cache's are checked every 12 hours if they are submitted to the cache.
Bad cache's are checked every 7 days once it has been found to be invalid.
This retry time will increment to 14 days after a set number of retries (4). This will continue until the retry time reaches 28 days.
Good caches that have recently been flagged as bad will be temporarily moved to the rejected url list. These caches will be checked every 12 hours until the cache is found to be in working order.
If the caches are still bad, they will then be checked every 12 hours until it reaches the retry threshold for that retry time (4 times). Retry times will then be 24, 36 and 48 hours respectively. Caches found to be bad after this period will then be upgraded to permanent failed status and will be checked every 7 days.
Q. I get errors when running Bazooka with CPanel. What's wrong?
CPanel may have some issues when files are created by PHP. PHP will create files under the username 'Nobody' which may stop your script from writing / working properly.
Work Around: Once the files have been created, navigate to the web address for
Bazooka. e.g. http://cache.myserver.com/g2/bazooka.php. This will create the default files for you. Next, download the contents of the "g2" folder onto your computer locally, then re-upload all the files back into the "g2" folder. This will upload
the files back into your account with the username for your account and you shouldnt
have any problems.
Q. How do I reset my data files?
To reset your data files, delete all *.dat files inside the directory that you have installed Bazooka. By deleting "bazooka.dat", you will trigger the re-creation of all necessary .dat files when "bazooka.php" is run.