All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Mike Marion <mmarion@qualcomm.com>
Cc: autofs@linux.kernel.org
Subject: Re: Seeing some 5.0.1 stop expiring mounts
Date: Thu, 19 Jul 2007 20:12:19 +0800	[thread overview]
Message-ID: <1184847139.3258.63.camel@raven.themaw.net> (raw)
In-Reply-To: <20070718213945.GA7455@cornholio.qualcomm.com>

On Wed, 2007-07-18 at 14:39 -0700, Mike Marion wrote:
> On Wed, Jul 18, 2007 at 02:46:07PM +0800, Ian Kent wrote:
> 
> > Might be worth considering going to 5.0.2, especially since you have a
> > busy site, as a nasty deadlock in the alarm handler has been fixed. 
> 

snip ...

> With the above patch applied to 5.0.1 (or using 5.0.2) as soon as the
> daemon gets a HUP signal, it flushes out all the auto.projects (our main
> map) entries from /proc/mounts and they're gone forever.

fwiw, the map-update-source-only patch is quite an important change from
the point of view of the version 5 design and the correct operation of
the map update logic. The reason it was needed is that I changed the way
instances of maps are sorted during initial development but didn't
properly account for it.

I really appreciate any time you can spare to help with this.

Thanks
Ian

  parent reply	other threads:[~2007-07-19 12:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 19:54 Seeing some 5.0.1 stop expiring mounts Mike Marion
2007-07-17 20:04 ` Mike Marion
2007-07-18  6:42   ` Ian Kent
2007-07-18  6:46 ` Ian Kent
2007-07-18 21:39   ` Mike Marion
2007-07-19 10:08     ` Ian Kent
2007-07-19 12:03     ` Ian Kent
2007-07-19 12:12     ` Ian Kent [this message]
2007-07-19 23:40       ` Mike Marion
2007-07-27  3:31         ` Ian Kent
2007-07-27 22:06           ` Mike Marion
2007-07-28  6:51             ` Ian Kent

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=1184847139.3258.63.camel@raven.themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --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.