From: "David Busby" <busby@edoceo.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: /dev/misc/inotify 0.11
Date: Tue, 5 Oct 2004 11:26:29 -0700
Message-ID: <82C88232E64C7340BF749593380762021166F5@seattleexchange.SMC.LOCAL>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <82C88232E64C7340BF749593380762021166F3@seattleexchange.SMC.LOCAL>
Importance: Normal
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1292
Lines: 32

> List,
>   I patched my 2.6.8.1 kernel with the inotify-0.11.  There 
> were some sample utils that in C that came with it.  Thanks.  
> I've successfully used those to work with inotify.  Here's what's bad:
> 
> 1> When I say `cat /dev/misc/inotify' my machine stops responding
> instantly.  I've not had a chance to see what happens.  I 
> know I'll not normally say that but when I say something else 
> dumb like cat /dev/misc/rtc cat will simply wait, not choke 
> up my whole system.
> 
> 2> Reading from /dev/misc/inotify with PERL produces the same effect.
> 
> I don't know enough about kernel hacking to really debug this 
> really well.  I peeked at the code and there still seems to 
> be calls to dnotify functions, can't I remove those?  I said this in
> drivers/char/inotify.c(54) static int inotify_debug_flags = 
> INOTIFY_DEBUG_ALL; so I'll recompile and see what happens.
> 
> 
> David Busby
> Edoceo, Inc.
> http://www.edoceo.com/

So now I upgraded to inotify-0.12 against the same kernel.  I'm still
having the same issues.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/