merge 306465 257876 thanks On Tue, Apr 26, 2005 at 09:31:09PM +0200, Jens Taprogge wrote:
> I have had problems with ypserv binding to port 636 a couple of times. > This port is also used by slapd. Since slapd is startes after nis, this > causes slapd to be unable to bind and thus fail. This is a general problem with network services that don't need a particular port and always has been. The kernel will quite happily hand out any old port if you don't specify one and they can easily get given something that another service wants to explictly bind to. > Obviously one work around the problem by specifying a port for ypserv to bind > to. But this does not make the default setup work. Well, it does work most of the time (as I say, there's always been the potential for this to go wrong). It does depend on the particular environment if something goes wrong - essentially, you've just been unlucky. > Perhaps nis should started after slapd? This won't help since the same issue applies in interaction with any service that needs a particular port. In any case, NIS has to start fairly early since it may be required for important filesystems (via autofs) and for accounts. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
