I believe (and this is based on hazy recollection from glancing at some article about the guts under either FAM or possibly BSD's kqueue comparing it against FAM) that the notifications are tracked at the inode level in the kernel. Each tracked inode has to have a pointer set to the notification routine, and if it's not NULL it gets called. The kernel doesn't have any way to know that you're even interested in children of the inode (hypothetically it could walk up the parent chain, but that'd add even more overhead to file access). I think you're pretty much going to have to explicitly walk the directory tree and request notification for all child directories.

--
We're looking for people in ATL

In reply to Re: SGI::FAM and use of coll by Fletch
in thread SGI::FAM and use of coll by cybersekkin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.