On Mon, Apr 28, 2003 at 01:17:28AM -0400, Jaldhar H. Vyas wrote: > On Sun, 27 Apr 2003, Matthias Urlichs wrote: > > > Hi, > > > > On Sun, 27 Apr 2003 08:26:48 +0000, Emmanuel Lacour wrote: > > > And I've got another question. Is there a way of handling "listen ports > > > conflicts" in debian. > > > > Of course there is. It's called "register your port with the maintainer of > > the /etc/services file". > > ...who is Anthony Towns ([EMAIL PROTECTED]) the maintainer of netbase. But > this is really only for "well-known ports" and I don't think either webmin > or zabbix count. > >
In unstable, there is a section in /etc/services: # # Services added for the Debian GNU/Linux distribution # and we can found ports for afbackup, sane, mandelspawn, xpilot, ... this are examples and I think a tool such as webmin could be in this section as well as those ones... Any way, for the zabbix package, I've started a discussion with the upstream author to change defaults ports. As you said in previous mail, webmin is widely used and I think it's a bad idea to use it's default port (10000) in zabbix, as it can make troubles to users. So it just remains the discussion: do we need to register ports in /etc/services or not ;-) And I think it's not debian specific, in general does any listen software be registered to IANA??? Do we have enough ports (~65535) for this? I don't think so. Currently, really known protocols are listed (<1024) such as smtp... And others software are "about" listed over 1024. But take a look here, http://www.iana.org/assignments/port-numbers, there is already conflicts for those ones. and: ndmp 10000/tcp Network Data Management Protocol ndmp 10000/udp Network Data Management Protocol webmin isn't listed;-) AW, the debian /etc/services isn't complete. Who choose the ports to be listed in debian /etc/services, and how? What is exactly the purpose of /etc/services: resolving ports as human readable names. But it's impossible to do a true resolution for all ports as we saw that there is a lot of conflicts over 1024... so maybe it's here only to avoid conflicts in a unix distribution and for resolving common ports (smtp, pop...). If it is so, maybe we need to add a section in the debian policy (i didn't see one...) and write how and who need to be registered. well, I stop here for now, as I've hit my english knowledge limit, and if I continue, I will write somethink noone could understand (or badly understand) ;-)
