Hi Paul & Kevin, we should add support for a customized port, maybe using a config option or an environment variable.
Paul: I suggest, that you change your Padre/Constant.pm in the meantime. It's very far from being perfect, but will be a quick fix (until the next update). Kevin: Pointing out that a port is reserved, isn't very helpful for a development system. I'm running up to three or four different webservers on different ports on a busy development day plus some databases, Memcache, Gearman, etc. A dev system commonly uses custom ports and a "standalone" software like Padre shouldn't block (other) development components which might not be as easy movable like Padre is. Regards, Sebastian On 08.04.2013 18:19, kevin dawson wrote: > On 2013-04-08 17:01, Paul CLaessen wrote: >> >> I noticed Padre is listening on TCP port 4444. >> >> Is there a way to either disable this, or change it to a different >> port number? >> >> (It conflicts with my openOCD server) >> >> And just out of curiosity, what is it used for? >> >> Kind regards, >> >> ~ Paul Claessen >> >> >> >> _______________________________________________ >> Padre-dev mailing list >> Padre-dev@perlide.org >> http://mail.perlide.org/mailman/listinfo/padre-dev > Paul, you are correct > > 1, what is it used for, > > set in Padre::Constant > > ##################################################################### > # Config Defaults Needed At Startup > > # Unlike on Linux, on Windows there's not really > # any major reason we should avoid the single-instance > # server by default. > # However during tests or in the debugger we need to make > # sure we don't accidentally connect to a running > # system-installed Padre while running the test suite. > # NOTE: The only reason this is here is that it is needed both during > # main configuration, and also during Padre::Startup. > use constant DEFAULT_SINGLEINSTANCE => ( WIN32 and not( > $ENV{HARNESS_ACTIVE} or $^P ) ) ? 1 : 0; > > # It would be better if we had fully dynamic collision awareness support, > # so that Padre could automatically port hop. > # In the mean time, just make sure that dev, test, and production versions > # of Padre use different ports, so they don't collide with each other. > use constant DEFAULT_SINGLEINSTANCE_PORT => ( > $ENV{PADRE_DEV} ? 4446 > : $ENV{HARNESS_ACTIVE} ? 4445 > : 4444 > ); > > 2, I think the conflict is all of your own doing see info below > > # Updated from http://www.iana.org/assignments/port-numbers and other > # sources like http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/services . > # New ports will be added on request if they have been officially assigned > # by IANA and used in the real-world or are needed by a debian package. > # If you need a huge list of used numbers please install the nmap package. > > have a look at -> > http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml > > regards > kevin > > > > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
