From: Ian Kent Subject: Re: Large number of mount request. Date: Sat, 08 Jul 2006 13:01:43 +0800 Message-ID: <1152334903.2814.6.camel@raven.themaw.net> References: <20060623112741.95825.qmail@web34505.mail.mud.yahoo.com> <007601c6a0af$aea99c70$251a17ac@ZyXEL.com> <1152187091.8761.6.camel@raven.themaw.net> <00b201c6a17a$8050d160$251a17ac@ZyXEL.com> <00ec01c6a1be$34af4e00$251a17ac@ZyXEL.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: , Sender: autofs-bounces@linux.kernel.org Errors-To: autofs-bounces@linux.kernel.org Content-Type: text/plain; charset="us-ascii" To: Latrell Cc: autofs@linux.kernel.org, ramana@intraperson.com On Fri, 2006-07-07 at 10:40 -0400, Jeff Moyer wrote: > ==> Regarding Re: [autofs] Large number of mount request.; "Latrell" adds: > > is85022> Sorry for misunderstanding what you mean. I think I should describe my > is85022> scenario in detail. > is85022> I use autofs to mount shares under user's home directory. It functions > is85022> normally in normal cases. > is85022> However, in stress test, the user continuously login->change directory > is85022> (autofs mount in this time) -> logout (a SIGERM sent to the automount > is85022> daemon) --> login....... > > Why is a SIGTERM sent to automount when you logout? It shouldn't be. I think Jeff has pretty much summed it up. The SIGTERM terminates autofs and you then have unnecessary startup and shutdown overhead giving a window where mounts will not work as there is no daemon to manage them. Don't forget that there was also a bug in the lock routines that cause it not to wait sometimes. Apply, at least the locking patch to 4.1.4. Ian