Torsten Landschoff cced. The short story is: slapd can fail to start if
one of the nis services grabs one of slapd's ports. My suggestion was to
move nis behind slapd in the startup process.
On Wed, Apr 27, 2005 at 12:37:16PM +0100, Mark Brown wrote:
> On Tue, Apr 26, 2005 at 11:29:06PM +0200, Je
On Tue, Apr 26, 2005 at 11:29:06PM +0200, Jens Taprogge wrote:
> The same is---or at least can be, if ldap is used for authentification
> and/or autofs map serving---true for slapd. But since nis is flexible
> in its use of ports it would make more sense IMHO to move it after slapd
> which binds
On Tue, Apr 26, 2005 at 09:35:01PM +0100, Mark Brown wrote:
> 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 a
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
Package: nis
Version: 3.13-2
Severity: normal
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.
Obviously one work around the problem by specifying a port
5 matches
Mail list logo
