All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Michael Orlov <orlovm@cs.bgu.ac.il>
Cc: autofs@linux.kernel.org
Subject: Re: autofs 5.0.4 and 5.0.5 do not remove ghost entries upon SIGHUP
Date: Thu, 13 Jan 2011 15:50:42 +0800	[thread overview]
Message-ID: <1294905042.2757.42.camel@perseus> (raw)
In-Reply-To: <20110111183424.7f0f7ad4@cs.bgu.ac.il>

On Tue, 2011-01-11 at 18:34 +0200, Michael Orlov wrote:
> Hi,
> 
> (I have sent this message on Oct 27, but nothing appears in the
> archives for that month - hopefully it's not a duplicate message.)
> 
> I think this is a bug - if it is not, I will be glad if someone
> corrects me. I am using autofs on Gentoo.

You will need to duplicate this with all the current 5.0.5 patches on
kernel.org applied to get serious interest in this here.

> 
> In auto.master, put
>   /mnt/test  /etc/auto.test  --ghost
> 
> In auto.test, put
>   floppy -fstype=auto :/dev/fd0
> (or anything similar)
> 
> 1. start autofs
> 2. see that /mnt/test/floppy exists
> 3. remove or comment out the "floppy" line in auto.test
> 4. send SIGHUP to autofs
> 
> After these actions, in autofs 5.0.4 / 5.0.5 (but not
> 5.0.3), /mnt/test/floppy still exists - it is not removed after SIGHUP.
> 
> This is problematic, for example, when auto.test is maintained via
> udev. Full restart of a service from a udev-invoked script is very
> error-prone.
> 
> Thanks,
> Michael
> 
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs

  reply	other threads:[~2011-01-13  7:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 16:34 autofs 5.0.4 and 5.0.5 do not remove ghost entries upon SIGHUP Michael Orlov
2011-01-13  7:50 ` Ian Kent [this message]
2011-01-13  9:16   ` Ian Kent
2011-01-13 14:36     ` Michael Orlov
2011-01-14  2:56       ` Ian Kent
2011-01-14  7:23         ` Michael Orlov
  -- strict thread matches above, loose matches on Subject: below --
2010-10-27 21:35 Michael Orlov

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=1294905042.2757.42.camel@perseus \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=orlovm@cs.bgu.ac.il \
    /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.