From: Oskar Liljeblad <oskar@osk.mine.nu>
To: linux-kernel@vger.kernel.org
Subject: Re: directory notifications lost after fork?
Date: Mon, 11 Mar 2002 09:50:06 +0100 [thread overview]
Message-ID: <20020311085006.GA1402@oskar> (raw)
In-Reply-To: <20020310210802.GA1695@oskar>
In-Reply-To: <20020310210802.GA1695@oskar>
On Sunday, March 10, 2002 at 22:02, usel wrote:
> The code snipper demonstrates what I consider a bug in the
> dnotify facilities in the kernel. After a fork, all registered
> notifications are lost in the process where they originally
> where registered (the parent process). [..]
FWIW, as long as you keep the child alive after fork the
notifications are not lost. Also the same effect when you
keep the parent(s) alive and decide to receive notification
in the newly created process instead.
Oskar Liljeblad (oskar@osk.mine.nu)
next prev parent reply other threads:[~2002-03-11 8:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 21:08 directory notifications lost after fork? Oskar Liljeblad
2002-03-11 7:41 ` Alex Riesen
2002-03-12 12:19 ` Jamie Lokier
2002-03-11 8:50 ` Oskar Liljeblad [this message]
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
[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-12 1:47 Malte Starostik
2002-03-12 12:55 ` Jamie Lokier
2002-03-12 16:37 ` Daniel Phillips
2002-03-12 17:21 ` Jamie Lokier
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=20020311085006.GA1402@oskar \
--to=oskar@osk.mine.nu \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox