From: Daniel Phillips <phillips@bonn-fries.net>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>,
Malte Starostik <malte@kde.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: directory notifications lost after fork?
Date: Tue, 12 Mar 2002 17:37:51 +0100 [thread overview]
Message-ID: <E16kpHc-0002Lx-00@starship> (raw)
In-Reply-To: <200203120247.05611.malte@kde.org> <20020312125543.B4281@kushida.apsleyroad.org>
In-Reply-To: <20020312125543.B4281@kushida.apsleyroad.org>
On March 12, 2002 01:55 pm, Jamie Lokier wrote:
> - dnotify causes files to notify their parent directory (yes it's
> ambiguous with hard links).
That's a bitch, isn't it? The only way I can think of to deal with it is via
a hardlink reverse map, and there are lots of worms in that can, including
where you store it, how much it costs to maintain it, how persistent it
should be and how to make it perfectly non-racy.
--
Daniel
next prev parent reply other threads:[~2002-03-12 16:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 1:47 directory notifications lost after fork? Malte Starostik
2002-03-12 12:55 ` Jamie Lokier
2002-03-12 16:37 ` Daniel Phillips [this message]
2002-03-12 17:21 ` Jamie Lokier
[not found] <20020311122701.A9718@riesen-pc.gr05.synopsys.com>
2002-03-11 19:34 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2002-03-10 21:08 Oskar Liljeblad
2002-03-11 7:41 ` Alex Riesen
2002-03-12 12:19 ` Jamie Lokier
2002-03-11 8:50 ` Oskar Liljeblad
2002-03-11 10:20 ` Alex Riesen
2002-03-11 10:26 ` Andrea Arcangeli
2002-03-12 1:04 ` Stephen Rothwell
2002-03-12 1:20 ` Andrea Arcangeli
2002-03-12 2:59 ` Stephen Rothwell
2002-03-12 4:01 ` Andrea Arcangeli
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=E16kpHc-0002Lx-00@starship \
--to=phillips@bonn-fries.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=malte@kde.org \
/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.