| To: | fam@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [fam] FAMAccessed event? |
| From: | Nathan Thompson-Amato <nathan.thompson-amato@xxxxxxxxxxxxxx> |
| Date: | Thu, 01 Nov 2001 17:13:06 -0500 |
| Cc: | Nathan Thompson-Amato <nathan.thompson-amato@xxxxxxxxxxxxxx> |
| Organization: | D.N. American |
| References: | <010701c15abd$d5da8030$144ba8c0@xxxxxxxxxxxxxxxxxxxxx> <3BE16AA1.4000707@xxxxxxxxxxxxxx> <006001c16320$48c86340$144ba8c0@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-fam@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012 |
Michael Wardle wrote: Yes, I believe so. If you look at Event.h, you will see these events: * Changed * Deleted * Executing * Exited * Created * Moved * Acknowledge * Exists * EndExist So you'll notice no Accessed event. Yeah, I was hoping maybe there was some clever workaround. :-) If so, is anybody interested in adding support for some kind ofFAMAccessed event? Not that I'm aware of. :-/ Okay. It looks like the dnotify interface provides an "accessed" event (according to http://www.linuxhq.com/kernel/v2.4/doc/dnotify.txt.html), so I think FAM could theoretically be patched to do this. I'll look into this further in the next day or two. Thanks again, Nathan -- 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> |
|---|---|---|
| ||
| Previous by Date: | Re: [fam] FAMAccessed event?, Michael Wardle |
|---|---|
| Next by Date: | [fam] Updated fam.spec file?, Nathan Thompson-Amato |
| Previous by Thread: | Re: [fam] FAMAccessed event?, Michael Wardle |
| Next by Thread: | [fam] Updated fam.spec file?, Nathan Thompson-Amato |
| Indexes: | [Date] [Thread] [Top] [All Lists] |