[1311] in Kerberos
RE: kerberos under SunOS
daemon@ATHENA.MIT.EDU (Bede B. McCall)
Tue Mar 26 15:46:35 1991
Date: Tue, 26 Mar 91 14:16:01 -0500
From: bede@linus.mitre.org (Bede B. McCall)
To: kerberos@MIT.EDU
Cc: Peter_Van_Epp%cc.sfu.CA@nnsc.nsf.net
In-Reply-To: Peter_Van_Epp%cc.sfu.CA@nnsc.nsf.net's message of Tue, 26 Mar 91 07:54:58 PST <2992136@cc.sfu.ca>
From: Peter_Van_Epp%cc.sfu.CA@nnsc.nsf.net
Date: Tue, 26 Mar 91 07:54:58 PST
There has been previous discussion that Kerberos needs to be started before
the port mapper other wise the portmapper owns all the ports and Kerberos
dies.
Mostly true, but it depends on your setup:
- If you aren't using yp, you can and probably should fire up
the Kerberos daemon(s) before portmap. This is also true if
your yp doesn't have a `services' map.
- If you are using yp with a `services' map, you have to wait
until the local ypserv and/or ypbind are running. These
depend on portmap, and your other daemons depend on the yp
`services' map to find their ports.
Sun's portmap assigns ports on the fly to RPC daemons, and these port
assignments generally tend to fall in the upper end of the
"privileged" range. Although portmap won't assign ports which are
already in use, it doesn't bother to consult the services database
when making port assignments, which can lead to disappointing and/or
unpredictable results.
The situation is the same with all versions of SunOS 4.n, incidentally.
-Bede B. McCall
The MITRE Corporation
Mail Stop A114
Burlington Road
Bedford, Massachusetts 01730 (617) 271-2839
Internet: bede@mitre.org
uucp: {decvax,philabs}!linus!bede
