All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Feist <cfeist@redhat.com>
To: David <spoel@xray.bmc.uu.se>
Cc: autofs@linux.kernel.org
Subject: Re: autofs not mounting from nis maps
Date: Wed, 16 Mar 2005 16:38:51 -0600	[thread overview]
Message-ID: <4238B57B.6000409@redhat.com> (raw)
In-Reply-To: <1111004718.6120.16.camel@studio.bibu>

What version of autofs are you using on the Fedora clients?  rpm -q autofs

Also, what appears in /var/log/messages when the mounts fail?

Thanks,
Chris

David wrote:
> Hi
> 
> I have a NIS server that broadcasts an auto.XXX files as such:
> 
> [root@appel2 proc]# ypcat -k auto.master
> /home  auto.home
> /usr/local  auto.local
> /pub auto.pub
> 
> [root@appel2 proc]# ypcat -k auto.home | head -8
> magnusa  hirst:/homes/hirst/dsk1/&
> hattne   hirst:/homes/hirst/dsk2/&
> maria  hirst:/homes/hirst/dsk2/&
> diane  hirst:/homes/hirst/dsk2/&
> alina dqs1:/user13/&
> guestji hirst:/homes/hirst/dsk2/&
> hanna hirst:/homes/hirst/dsk2/&
> gunilla  bacon:/Users/&
> 
> ...
> 
> On the client side roughly half of the directories are actually mounted
> when I cd into them, the other half give:
> [root@appel2 proc]# cd /home/magnusa
> -bash: cd: /home/magnusa: No such file or directory
> 
> Without NIS everything works fine. However I have a few tens of
> workstations so it's quite tedious to update all machines with new files
> and restart autofs whenever something changes.
> 
> Am I doing something terribly wrong? Any other tips?
> 
> We are running debian on the servers and different Fedora's on the
> clients.
> 

  reply	other threads:[~2005-03-16 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 20:25 autofs not mounting from nis maps David
2005-03-16 22:38 ` Chris Feist [this message]
2005-03-16 23:31 ` Jim Carter
2005-03-17  8:24   ` David
2005-03-17  8:29   ` David
2005-03-17 17:54     ` Michael Blandford

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=4238B57B.6000409@redhat.com \
    --to=cfeist@redhat.com \
    --cc=autofs@linux.kernel.org \
    --cc=spoel@xray.bmc.uu.se \
    /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.