All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: "Rigler, Stephen C." <srigler@marathonoil.com>
Cc: autofs mailing list <autofs@linux.kernel.org>,
	Ian Kent <raven@themaw.net>
Subject: Re: [ANNOUNCE] autofs 5.0.0 beta1
Date: Thu, 04 May 2006 14:03:47 -0400	[thread overview]
Message-ID: <x49ac9xy8e4.fsf@redhat.com> (raw)
In-Reply-To: <C3CDA0E3AC8B4E438E94F37D0A20FE71026B10D5@HOUEXC210.mgroupnet.com> (Stephen C. Rigler's message of "Thu, 4 May 2006 12:29:54 -0500")

==> Regarding RE: [autofs] [ANNOUNCE] autofs 5.0.0 beta1; "Rigler, Stephen C." <srigler@marathonoil.com> adds:

>> -----Original Message----- From: Jeff Moyer [mailto:jmoyer@redhat.com]
>> Sent: Thursday, May 04, 2006 8:56 AM To: Ian Kent Cc: Rigler, Stephen
>> C.; autofs mailing list Subject: Re: [autofs] [ANNOUNCE] autofs 5.0.0
>> beta1
>> 
raven> and /etc/auto.master exists with a +auto.master it
>> will probably get
raven> it wrong in a strange way. Maybe that's what is happening?
>> Yeah, I think this is the one exception to the nsswitch rule. I wonder
>> if it's the same if you have /etc/auto.foo that does a +auto.foo?  May
>> be worth testing that out on another UNIX box to see what happens.
>> 
>> -Jeff
>> 

srigler> Pretty much standard configuration here on Solaris and Irix is to
srigler> have "automount: files nis" in nsswitch.conf and "+auto.master" in
srigler> the local auto_master file.  I'm not aware if this is what the
srigler> standard automount behavior should be (it's documented in the Irix
srigler> man page for autofs), but we've gotten away with it for years if
srigler> it's not.

srigler> Another nice thing to see would be the "-null" option in
srigler> auto.master.  We have machines running clustered filesystems that
srigler> are also exported via NFS from one or two meta-data servers.  The
srigler> machines that see the filesystems locally should not automount the
srigler> fileystems and the "-null" would allow us to exclude them.

Well, you're in luck.  Give autofs5 a try, as it is supposed to handle
-null maps.

-Jeff

  reply	other threads:[~2006-05-04 18:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 17:29 [ANNOUNCE] autofs 5.0.0 beta1 Rigler, Stephen C.
2006-05-04 18:03 ` Jeff Moyer [this message]
2006-05-05  1:37 ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2006-05-08 11:51 Rigler, Stephen C.
2006-05-09 10:51 ` Ian Kent
2006-05-04 13:08 Rigler, Stephen C.
2006-05-04 13:57 ` Jeff Moyer
2006-05-04 11:16 Rigler, Stephen C.
2006-05-04 12:29 ` Ian Kent
2006-05-04 13:56   ` Jeff Moyer
2006-05-02 15:35 Ian Kent
2006-05-02 17:33 ` Steinar H. Gunderson
2006-05-03  1:26   ` Ian Kent
2006-05-03 13:16 ` Moshe Kaminsky
2006-05-03 14:48   ` Ian Kent
2006-05-03 16:55     ` Moshe Kaminsky
2006-05-03 17:30       ` Ian Kent
2006-05-04 17:33         ` Moshe Kaminsky
2006-05-05  1:32           ` Ian Kent
2006-05-03 15:15   ` Ian Kent
2006-05-03 16:58     ` Moshe Kaminsky
2006-05-03 15:58   ` Ian Kent
2006-05-03 17:00     ` Moshe Kaminsky
2006-05-03 17:56       ` Ian Kent
2006-05-04 17:28         ` Moshe Kaminsky

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=x49ac9xy8e4.fsf@redhat.com \
    --to=jmoyer@redhat.com \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.net \
    --cc=srigler@marathonoil.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.