From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org, Ronald Kuetemeier <ron_ker@kuetemeier.com>
Subject: [PATCH][DOCO] Re: 2.6.0-test3 and dnotify
Date: Wed, 13 Aug 2003 14:37:51 +1000 [thread overview]
Message-ID: <20030813143751.3dc0b14b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1060705727.1189.12.camel@ronald.kuetemeier.com>
Linus,
On 12 Aug 2003 10:28:47 -0600 Ronald Kuetemeier <ron_ker@kuetemeier.com> wrote:
>
> I run some of my programs on 2.6.0-test3 this morning, before my coffee
> ..., anyhow seems dnotify isn't working any more. I compiled the example
> from <linux-2.6.0-test3>/Documentation/dnotify.txt this also doesn't
> work anymore.
This has been asked a couple of times, so can you please apply the
following documentation patch?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
diff -ruN 2.6.0-test3/Documentation/dnotify.txt 2.6.0-test3.sfr.1/Documentation/dnotify.txt
--- 2.6.0-test3/Documentation/dnotify.txt 2001-04-07 03:42:48.000000000 +1000
+++ 2.6.0-test3.sfr.1/Documentation/dnotify.txt 2003-08-13 14:32:14.000000000 +1000
@@ -32,7 +32,8 @@
Preferably the application will choose one of the real time signals
(SIGRTMIN + <n>) so that the notifications may be queued. This is
-especially important if DN_MULTISHOT is specified.
+especially important if DN_MULTISHOT is specified. Note that SIGRTMIN
+is often blocked, so it is better to use (at least) SIGRTMIN + 1.
Implementation expectations (features and bugs :-))
---------------------------
@@ -78,10 +79,10 @@
act.sa_sigaction = handler;
sigemptyset(&act.sa_mask);
act.sa_flags = SA_SIGINFO;
- sigaction(SIGRTMIN, &act, NULL);
+ sigaction(SIGRTMIN + 1, &act, NULL);
fd = open(".", O_RDONLY);
- fcntl(fd, F_SETSIG, SIGRTMIN);
+ fcntl(fd, F_SETSIG, SIGRTMIN + 1);
fcntl(fd, F_NOTIFY, DN_MODIFY|DN_CREATE|DN_MULTISHOT);
/* we will now be notified if any of the files
in "." is modified or new files are created */
next prev parent reply other threads:[~2003-08-13 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 16:28 Ronald Kuetemeier
2003-08-13 4:29 ` Stephen Rothwell
2003-08-13 4:37 ` Stephen Rothwell [this message]
2003-08-13 17:13 ` [PATCH][DOCO] " Ronald Kuetemeier
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=20030813143751.3dc0b14b.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ron_ker@kuetemeier.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®