My error, it is 1023.   And now that you mention it, services have a list of
ports and an english translation.  It is used by netstat to "translate" the
names.

Mark

Kimbro Staken wrote:

> On Wednesday, March 13, 2002, at 10:51 AM, Mark J. Stang wrote:
>
> > Kimbro/Tom/et. al.,
> > �yvind brings up a pretty good point, the default port number is below the
> > reserved
> > number of 5000.   If I remember correctly, all ports below 5000 are known
> > as
> > "Well Known Ports" and are supposed to be reserved.   I think XmlBlaster
> > recently
> > requested that their particular port be reserved for them.
>
> Well known ports are 1023 and below. You can reserve other ports but IANA
> doesn't really control anything above 1023 and most apps don't bother with
> registering. In reality we should be using an alt-http port but we
> explicitly avoided that because it is so easy to conflict with another
> process. i.e. 8080 is the default for Tomcat and a bunch of other things
> and 8008 isn't much better.
>
> > By reserving ports and adding them to the services file, we eliminate the
> > possibility
> > that the OS would "give away" our port.   *nix platforms grab unassigned
> > ports
>
> Are you sure the services file is used for this purpose?
>
> > whenever someone needs a port.   It does this by starting at the ones
> > above
> > the
> > reserved ports and then keeps on going.   Eventually, it rotates back and
> > starts all
> > over.   Windows on the other hand just starts at the begining every time
> > and
> > keeps
> > reusing ports.
> >
> > Anyway, the port that xindice uses is usually reserved for root access
> > only
> > on some
>
> It's ports 1023 and below that are reserved for root access.
>
> > machines.   So, we probably should a default that is above the reserved
> > limit.  Or
> > maybe provide a better message?   I don't know, what does everyone else
> > think?
> >
> > Mark
> >
> > �yvind Vestavik wrote:
> >
> >> First of all:
> >> Thank you Mark for your effort to help me.
> >> I really appreciate it.
> >>
> >> After two days i finally found that my problems getting Xindice
> >> started had nothing to do with any environement variables as I had
> >> thought. It had to do with
> >> the fact that the servers http service is running om rel. low portnumber.
> >> These are (at least on the machine I'm working on) reserved for processes
> >> running as root. I don't have access to root. When the http service
> >> couldn't start, the API service couldn't start either.
> >>
> >> By simply changing the port number of the http service in the
> >> XINDICE_HOME/config/system.xml I managed to get the server up and running
> >> in no time :-)
> >>
> >> In case someone run into the same problem..
> >>
> >> �yvind
> >>
> >> �yvind Vestavik
> >> �vre M�llenberggt 44b
> >> 7014 Trondheim
> >> [EMAIL PROTECTED]
> >> 41422911
> >
> >
> Kimbro Staken - http://www.kstaken.org - http://www.xmldatabases.org
> Apache Xindice native XML database http://xml.apache.org/xindice
> XML:DB Initiative http://www.xmldb.org
> Senior Technologist (Your company name here)

Reply via email to