All of lore.kernel.org
 help / color / mirror / Atom feed
From: Farkas Levente <lfarkas@bppiac.hu>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: automount never umount
Date: Tue, 22 Nov 2005 17:19:03 +0100	[thread overview]
Message-ID: <438344F7.8020503@bppiac.hu> (raw)
In-Reply-To: <Pine.LNX.4.63.0511222054060.2600@donald.themaw.net>

Ian Kent wrote:
> That wasn't what I had in mind.
> 
> I was thinking more along the lines of the definition of what constitues 
> "use". For example any access, such as a directory listing, will update 
> the "last used" value whereas if I change the definition of "last used" to 
> "currently in use" then to be busy there would have to be an open file or 
> a process working directory set. This may solve the GUI scanning problem 
> we see but wouldn't solve immediate remounting that occurs due to the 
> scanning as well.

that would be useful and may be solve our problem. without it the
current implementation is not usable to umount. think about just the
daily process like slocate database update, tripwire and may be others.

-- 
  Levente                               "Si vis pacem para bellum!"

  reply	other threads:[~2005-11-22 16:19 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 15:31 automount never umount Farkas Levente
2005-11-22 13:27 ` Ian Kent
2005-11-22  9:43   ` Farkas Levente
2005-11-22 13:03     ` Ian Kent
2005-11-22 16:19       ` Farkas Levente [this message]
2005-11-22 16:50         ` Jeff Moyer
2005-11-22 21:24           ` Farkas Levente
2005-11-22 23:27             ` Ian Kent
2005-11-23  0:24             ` Jeff Moyer
2005-11-23  9:27               ` Farkas Levente
2005-11-23 13:13                 ` Ian Kent
2005-11-23 13:18                   ` Farkas Levente
2005-11-23 15:28                     ` Jeff Moyer
2005-11-23 15:38                       ` Ian Kent
2005-11-23 16:57                         ` Jeff Moyer
2005-11-23 17:13                           ` Farkas Levente
2005-11-23 17:16                             ` Jeff Moyer
2005-11-24 10:05                               ` Farkas Levente
2005-11-24 12:10                                 ` Ian Kent
2005-11-24 23:17                                   ` Farkas Levente
2005-11-28 15:41                                   ` Jeff Moyer
2005-11-28 16:11                                     ` Ian Kent
2005-11-29 12:28                                     ` Farkas Levente
2005-12-01  9:31                                       ` Farkas Levente
2005-12-01 11:03                                         ` Ian Kent
2005-12-01 11:36                                           ` Farkas Levente
2005-12-01 12:57                                             ` Jeff Moyer
2005-12-01 13:41                                               ` Farkas Levente
2005-12-01 15:02                                                 ` Ian Kent
2005-12-01 13:45                                             ` Ian Kent
2005-12-01 13:53                                               ` Farkas Levente
2005-12-01 15:04                                                 ` Ian Kent
2005-11-23 14:26               ` Ian Kent
2005-11-22 23:18           ` 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=438344F7.8020503@bppiac.hu \
    --to=lfarkas@bppiac.hu \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.net \
    /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.