All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Blandford <mlblandf@sedona.ch.intel.com>
To: Dylan <autofs@dylan.me.uk>
Cc: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: autofs4 and NIS
Date: Mon, 05 Jan 2004 09:21:51 -0700	[thread overview]
Message-ID: <3FF98F1F.6010709@sedona.intel.com> (raw)
In-Reply-To: <200401010159.12640.autofs@dylan.me.uk>

Dylan wrote:

>Hello all,
>
>I'm currently using autofs4 to mount nfs shares. The config files are 
>distributed via NIS, which overall is working without a hitch. I have 
>two related problems, however...
>
>It is, obviously, necessary to restart the NIS server from time to time, 
>in order to take account of config changes (usually changes to user 
>accounts.) When I do this, the following occurs:
>  
>
I think we need to address this issue in particular.  I can't think of 
any reason you need to restart your NIS master for config changes.  We 
have masters/slaves that have been up for years at a time without 
restarting.  These probably see > 100 map changes/pushes a day.  What 
changes are being made that a 'make' in /var/yp doesnt solve?

Also, you can set up a NIS slave/secondary to handle any connections in 
the event the master is unavailable or to help handle the load.  Then 
you always have NIS coverage.

I think if you solve this problem, the others will become non issues. 

Michael

      parent reply	other threads:[~2004-01-05 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-01  1:59 autofs4 and NIS Dylan
2004-01-01  4:13 ` Ian Kent
2004-01-05 15:28 ` Todd Denniston
2004-01-05 16:21 ` Michael Blandford [this message]

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=3FF98F1F.6010709@sedona.intel.com \
    --to=mlblandf@sedona.ch.intel.com \
    --cc=autofs@dylan.me.uk \
    --cc=autofs@linux.kernel.org \
    /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.