All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Bradner <gregb@rhythm.com>
To: Michael Blandford <mlblandf@sedona.ch.intel.com>
Cc: autofs@linux.kernel.org, Mike Marion <mmarion@qualcomm.com>,
	Annie Mckeon <anne.bourgeois@analog.com>
Subject: Re: Strange autofs V4.0 problems
Date: Tue, 03 Feb 2004 10:46:28 -0800	[thread overview]
Message-ID: <401FEC84.40704@rhythm.com> (raw)
In-Reply-To: <401EE1BC.2020006@sedona.intel.com>

use the 'nonstrict' opition in your auto.net script.

Michael Blandford wrote:

> Mike Marion wrote:
>
>>
>> The fact that you're seeing that in your logs shows that autofs is 
>> working fine.. your host tried to mount the directory and was denied 
>> by the server.  I'm seeing the exact same thing for some new linux 
>> boxes I just installed over the weekend and some of our NetApp 
>> filers, and we're seeing the same thing from some new Solaris hosts 
>> as well.
>>
>> I'm wondering if there's some kind of name/ip caching bug on the 
>> netapps that caches a deny for a very long period if you try to mount 
>> before your netgroups/dns is updated with the new host information.
>
>
>
> If you can mount them by hand on the same box not using autofs, then 
> it seems more likely to be an autofs issue.
>
> Michael
>
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rhythm & Hues
5404 Jandy Place
Los Angeles, CA 90066
Voice: 310 448-7763
Fax:   310 448-7600
gregb@rhythm.com

  parent reply	other threads:[~2004-02-03 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02 20:51 Strange autofs V4.0 problems Alan.Burke
2004-02-02 23:30 ` Mike Marion
2004-02-02 23:48   ` Michael Blandford
2004-02-03  0:59     ` mmarion
2004-02-03 22:07       ` mmarion
2004-02-03 18:46     ` Greg Bradner [this message]
2004-02-03 19:14       ` Anne.Bourgeois

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=401FEC84.40704@rhythm.com \
    --to=gregb@rhythm.com \
    --cc=anne.bourgeois@analog.com \
    --cc=autofs@linux.kernel.org \
    --cc=mlblandf@sedona.ch.intel.com \
    --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.