Ensuring inetd is started before any RPC services

[Oliver Fromme]

Trond Endrestøl wrote:
 > I have on many occasions run into the situation where the RPC based 
 > services have occupied the well-known ports for other non-RPC based 
 > services. Last week rpc.lockd on one of my systems got hold of TCP 
 > port 995, leaving inetd unable to start any pop3s services.

Yes, that's annoying.

I think a simple work-around for the problem is to lower
the sysctl net.inet.ip.portrange.lowfirst.  The default
is 1023.  If you don't need any other ports right beneath
995, then you can set it to 994 via /etc/sysctl.conf.
Then the RPC-based services that don't use fixed ports
should start using port numbers from 994 downwards.

Best regards
   Oliver

-- 
Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"I learned Java 3 years before Python.  It was my language of
choice.  It took me two weekends with Python before I was more
productive with it than with Java." -- Anthony Roberts