fam
[Top] [All Lists]

[fam] Re: fam & imon

To: rusty@xxxxxxx
Subject: [fam] Re: fam & imon
From: Andrew Morton <andrewm@xxxxxxxxxx>
Date: Wed, 29 Mar 2000 07:15:25 +0000
Cc: fam@xxxxxxxxxxx
References: "Andrew Morton" <morton@xxxxxxxxxxxxxxxxxx> "fam & imon" (Mar 21, 6:52am), <38D71C1E.AE0E8BF1@xxxxxxxxxxxxxxxxxxxxx> <10003212313.ZM296614@xxxxxxxxxxxxxxxxxx>
Sender: owner-fam@xxxxxxxxxxx
Rusty Ballinger wrote:
> 
> > You guys were very quiet about this patch....
> 
> Yeah... that wasn't exactly the plan,

Hi, Rusty.  Thanks for the reply.

Unfortunately my stated intention to look at imon in "2-4 weeks time"
isn't looking good at present :-(

Am I right in my understanding that this facility tells interested
userland applications two main things:

1: That an executable is currently being executed and

2: That an inode has been altered?

If so, I'm wondering how much value number 1 provides.  For desktop file
browsers, number 2 is more important?

Also, there are many, many other applications which could benefit from
number 2.  Any sort of app which monitors logfiles or spool
directories.  'tail -f', come to that.

If I'm not missing something, have you considered splitting off feature
1 and submitting only the inode-mod feature?  If this reduces the
intrusiveness of the kernel patch this may ease its path into the
mainstream release.



-- 
-akpm-

--
Source code, list archive, and docs: http://oss.sgi.com/projects/fam/
To unsubscribe: echo unsubscribe fam | mail majordomo@xxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>