From: "Bryan O'Sullivan" Subject: Re: Severe problem with 4.1.2: automount caches NIS maps forever Date: Sat, 08 May 2004 14:26:55 -0700 Sender: autofs-bounces@linux.kernel.org Message-ID: <1084051615.2073.5.camel@camp4.serpentine.com> References: <1083865163.18740.6.camel@serpentine.internal.keyresearch.com> <409AAC9E.9000505@sedona.intel.com> <1083952697.18740.86.camel@serpentine.internal.keyresearch.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autofs-bounces@linux.kernel.org Content-Type: text/plain; charset="us-ascii" To: raven@themaw.net Cc: autofs@linux.kernel.org On Fri, 2004-05-07 at 22:44, raven@themaw.net wrote: > Dealing with mount fails is often a source of pain for a bunch of reasons. > I think the idea of using that as a trigger to re-read the map is likely > not the best as this is potentially the time the map might not be available. Right, which is why I suggest dropping the TTL instead of taking immediate action. Frankly, if NIS or LDAP is hosed and you're relying on them for directory services, it is unlikely to matter whether or not autofs "works", since so much else (i.e. regular user stuff) is going to be hosed.