Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible Port Conflicts #4

Open
crazy2be opened this issue Jun 14, 2011 · 1 comment
Open

Possible Port Conflicts #4

crazy2be opened this issue Jun 14, 2011 · 1 comment

Comments

@crazy2be
Copy link
Owner

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
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant