From: Ian Kent <raven@themaw.net>
To: Mike Marion <mmarion@qualcomm.com>
Cc: autofs@linux.kernel.org
Subject: Re: Ldap starting nis child?
Date: Wed, 07 Feb 2007 22:54:38 +0900 [thread overview]
Message-ID: <1170856478.3415.8.camel@raven.themaw.net> (raw)
In-Reply-To: <20070206224910.GI21027@cornholio.qualcomm.com>
On Tue, 2007-02-06 at 14:49 -0800, Mike Marion wrote:
> We're looking into some odd issue we're starting to have with our ldap
> autofs setup, and as I test I tried starting our direct map daemon
> without the --ghost flag, and it failed miserably. the main moint
> points started properly (--debug was on) like so:
> automount[3217]: starting automounter version 4.1.4, path = /prj, maptype = ldap, mapname =
> automountmapname=auto.projects,ou=automountMaps,ou=sandiego,ou=qct,dc=qualcomm,dc=com
>
> But as soon as you tried to traverse that, it spawned a maptype=yp
> child:
> automount[7893]: starting automounter version 4.1.4, path = /prj/vlsi, maptype = yp, mapname =
> automountmapname=auto.projects,ou=automountMaps,ou=sandiego,ou=qct,dc=qualcomm,dc=com
>
> Which eventually failed with a "RPC failure on NIS operation" and
> bombed.
To be honest, if you need to use direct maps, use version 5 and a recent
enough kernel. You can check the kernel patches in the tarball to work
out how much is in each kernel.
>
> We're using 4.1.4 and have all the patches applied to the daemons.
> Using a sles10 2.6.16.21-0.8smp kernel (has latest kernel patches, or at
> least these: autofs4-2.6.10-20050404.patch).
If you really must use v4 then use a more recent kernel and/or use the
patches in the v5 tarball and send a debug log.
Ian
next prev parent reply other threads:[~2007-02-07 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 22:49 Ldap starting nis child? Mike Marion
2007-02-07 13:54 ` Ian Kent [this message]
2007-02-07 16:11 ` Jeff Moyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1170856478.3415.8.camel@raven.themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=mmarion@qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.