Possible Port Conflicts

[crazy2be]

Due to hard-coded listening ports in each of the modules, it's very possible that two modules could end up listening on the same port. The framework should solve this by automatically assigning ports to modules, either by making a config file in each jail upon start like this:

# Automatically generated module config file
port=:8081 # One possibility
listenon=localhost:8081 # Another possibility

Or, alternatively, by passing it as a -port=":8081" command-line argument. Not sure which solution is best at this point.

[crazy2be]

The framework will most certainly need to manage these things if we want to move to automatic management across multiple servers. Currently I'm going for the -port= command line option, as it seems least intrusive and most intuitive.