"Jay Savage" <[EMAIL PROTECTED]> writes:
> Where is all this headed? File monitoring relies on Step 4. Step 4 is
> where the directory pointers and block counts get updated, and the
> ctime and mtime get rewritten. Once your system performs Step 4,
> File::Monitor will see the change on its next r
On Jan 25, 2008 12:20 PM, <[EMAIL PROTECTED]> wrote:
> "Jay Savage" <[EMAIL PROTECTED]> writes:
>
> > Finally, Tom's points are important. How do you *know* that the files
> > (in this case a single directory) changed *during the sleep*? Do you
> > know that the output wasn't buffered? That the sy
On Jan 25, 2008 9:20 AM, <[EMAIL PROTECTED]> wrote:
> How long of a sleep would be required to *KNOW* a change has happened
> with something external writing to files?
You want to be sure the other task is finished? Several days of
waiting should suffice for better than 99.999% of all cases. If
"Jay Savage" <[EMAIL PROTECTED]> writes:
> Finally, Tom's points are important. How do you *know* that the files
> (in this case a single directory) changed *during the sleep*? Do you
> know that the output wasn't buffered? That the system didn't delay the
> writes for some reason? That you were e
"Jay Savage" <[EMAIL PROTECTED]> writes:
[...] Thanks for the pointers
> Finally, Tom's points are important. How do you *know* that the files
> (in this case a single directory) changed *during the sleep*? Do you
> know that the output wasn't buffered? That the system didn't delay the
> writes
"Tom Phoenix" <[EMAIL PROTECTED]> writes:
> On Jan 24, 2008 12:34 PM, <[EMAIL PROTECTED]> wrote:
>
>> Can anyone provide a real example of using File::Monitor?
>
> Aren't the examples in the docs and the t/ directory "real" enough for
> you? There's even a file in the examples/ directory; it look
On Jan 24, 2008 3:34 PM, <[EMAIL PROTECTED]> wrote:
> What I really want to do is monitor a directory recursively but here
> just trying to use it any basic way to start to `get' how to use it.
>
For starter, you haven't turned on the recurse flag. Take another look
at the arguments to File::Mon
On Jan 24, 2008 12:34 PM, <[EMAIL PROTECTED]> wrote:
> Can anyone provide a real example of using File::Monitor?
Aren't the examples in the docs and the t/ directory "real" enough for
you? There's even a file in the examples/ directory; it looks pretty
real to me. Does it work for you?
http
Can anyone provide a real example of using File::Monitor?
I've been pounding away at perldoc File::Monitor, which seems to be
pretty thoroughly documented but as often seems to happen to me
its just not soaking in... how the scanning and reporting is supposed
to happen. Somehow in the course
