That is easy enough to check at install time :) If we want to avoid that scenario the following could be done:
- Check if anything is using port 80 at config time, warn and don't config anything if it is - Load/Unload the redirect rule on tomcat startup, this will make port 80 available to other processes when tomcat is stopped - Listen on port 80 with an empty connector to grab hold of the port (throwing a warning to the user launching httpd as a separate process that the port is in use) On Tue, May 12, 2015 at 3:34 PM, Erik Weber <terbol...@gmail.com> wrote: > On Tue, May 12, 2015 at 3:30 PM, Rafael Fonseca <rsafons...@gmail.com> > wrote: > > > Keeping a couple of config files for httpd/nginx should be quite easy, we > > could configure it optionally (with a prompt) when running the > > cloud-setup-management script, for instance. > > We can optionally also just configure a redirect rule for port 80 on the > > same prompt if user doesn't want proxying, that way it will be reachable > > both on port 80 AND 8080 :) > > > > > > That could easily lead to confusion if the user is running something else, > like httpd, on port 80. > > Although I like the efforts made to make things easier, assumptions is a > bad thing. > > -- > Erik >
