Initial Checklist
Server Information
Server Name/Location:
Choose a name for your server, and provide some details of where it
is physically located.
zone refers to the basic region of the world that your server is in.
Allowable values for zone are:
af Africa (including South Africa)
an Antarctica
ap Asia-Pacific
au Australia
ca Canada
eu Europe (including former Soviet republics)
sa South America
us United States of America
area refers to the more specific region within the zone that
your server is in. For Antarctic, Australian, Canadian and North American servers,
area will be a two letter state abbreviation. For all other servers,
area will be the two letter ISO code for the country your server is
in.
Your server name may be anything you wish, you should have some kind
of idea what sort of names will 'fit in' with the other servers on our net by
now. It may be up to 80 characters in length.
eg. penguin.uk.eu.blitzed.org
eg. porkscratchings.pa.us.blitzed.org
Now we need some more geographical information for displaying your server
on our servers page should you be linked. Sorry
if this seems redundant after what you specified above, however that was to
create the server name whereas this is meant to be human-readable.
IP address:
Please specify the IP address of your actual IRCd. i.e. we should be
able to connect to your IRC server via this address.
eg. 12.34.56.78
Ports:
The ports that your IRCd will accept connections on. You must
include 6667, 7000 and 7500. Specify as a list of comma-separated
integers. Use '-' to show ranges.
eg. 6667, 6690-7000, 7500
Operating System:
Please provide a short explanation of the operating system / unix
distribution you will be using.
e.g. Red Hat Linux 7.1 kernel version 2.4.4.
Memory:
State how much memory is installed in your server.
16 -> 31MB
32 -> 63MB
64 -> 127MB
128 -> 255MB
256 -> 511MB
512 -> 767MB
768 -> 1023MB
1024MB+
CPU:
Provide some information on the proccessor's type and speed.
e.g. AMD Athlon 1GHz
Other Tasks:
State any other tasks the machine performs.
e.g. mail, httpd, eggdrop bots.
File Descriptors:
Number of file descriptors in kernel. In Linux, ulimit -a will
show you this information.
e.g. 1024.
Maximum Clients:
How many clients you will allow on your server. Leave this at 0 if you're
prepared to allow any number.
e.g. 500
Internet Routing Information
Connectivity:
Please provide a detailed description of your server's connectivity to the
rest of the world.
Warning: Blitzed's Admin team and/or routing secretary will verify any information in this
application to ensure correctness, consistency and validity. Please ensure the information
you are providing is real and correct . Applicants that falsify
anything on their application may have their application revoked, and be barred
from ever re-applying to Blitzed.
Personal Details
Admin Details:
Please double-check these details,
as they are very important.
Free Answer (Use as much space as needed)
Your involvement with Blitzed
Please describe the ways you have been involved with Blitzed, and why you
feel your server should become part of Blitzed.
Do you have any IRC Operators in mind?
Bear in mind that your server may have a maximum of four operators,
including you and your coadmin if you choose to have one. Please supply full
name and email address of any opers. Note also that once your application is
submitted you may not alter your staff until after your test link period is
over.
How much time would you expect to be able to dedicate to Blitzed?
How much active time would you estimate you will be able to Blitzed per
week? There are approximately 112 waking hours in a week; be realistic.
Roughly hours
Please enter an integer.
Server Situation
Please provide name and contact information for someone with authority over
the CPU and bandwidth utilization of your server. Please indicate if this
server is co-located (i.e. you are personally paying for bandwidth), ISP
sponsored or has some other arrangement.
Your IRCd Experience
Please provide a brief summary of your personal experience running
ircds and list any other relevant technical skills.
Bot Policy
What will your policy on bots be?
eg. "Friendly bots allowed"
If The Worst Happens...
What action will you take if your server's performance becomes a detriment
to the operation of Blitzed?
Extra Comments
Use this space if you would like to add something not already mentioned:
NB This field is optional.
Pings and Traceroutes
Obtain either :
Output from "mtr -rc 50 " for every Blitzed server.
ie: for s in
cabernet cookies ouzo penguin sausage tabasco vindaloo ;do echo $s >> mtr; mtr -rc 50 $s.blitzed.org >> mtr; echo >> mtr;done
or :
A set of ping s for every Blitzed server. Send 20 ping requests to
each server and include the average's output as well.
A set of traceroute s for every Blitzed server.
mtr is preferred and will save you and us time . If your
server does not have mtr, download and install it from http://www.bitwizard.nl/mtr/ The
servers you must mtr or ping +traceroute are as
follows:
cabernet.ca.us.blitzed.org
cookies.on.ca.blitzed.org
ouzo.nl.eu.blitzed.org
penguin.uk.eu.blitzed.org
sausage.tx.us.blitzed.org
tabasco.uk.eu.blitzed.org
vindaloo.uk.eu.blitzed.org
Paste the results into the textbox below:
Applications without this information will not be accepted.
Final Checklist:
I have checked that all my details have been filled in correctly.