Re: dnotify oddity in 2.4.19pre6aa1

[Kurt Wall <kwall@kurtwerks.com>]

Scribbling feverishly on May 03, Stephen Rothwell managed to emit:
> Hi Andrew,
> 
> Sorry I have been a bit slow on this.
> 
> On Tue, 23 Apr 2002 09:58:14 -0700 Andrew Burgess <aab@cichlid.com> wrote:
> >
> > I am seeing something very strange with the dnotify feature in kernel
> > 2.4.19pre6aa1. I'm developing a file copy daemon that makes backups of
> > files as soon as they change so I run dnotify on every directory in my
> > system (essentially). I based my program on the example in dnotify.txt
> > in the Documentation directory.
> 
> So far, so good :-)
> 
> > I notice that after a while two things happen:
> > 
> > 1) In my copyd process I start getting signals for directories that are
> > not changing. Even stranger, I get signals for fd that I've never
> > opened.
> 
> OK, this is weird, but I am looking into it.
> 
> > 2) Other processes, like sendmail, start exiting with the same signal
> > (RTMIN+5). (I use +5 because I started seeing the problem with +0 and I
> > took a wild guess that RTMIN+0 was being used for something else).

glibc reserves RTMIN+[012] for its own use, so you have to use
RTMIN+[n>2].

[...]

Kurt
-- 
Command, n.:
	Statement presented by a human and accepted by a computer in
such a manner as to make the human feel as if he is in control.