The various examples in the synopsis of File::Monitor are not all consistent with each other and you have copied some of the inconsistencies into your program. In particular, you create a $monitor object but then try to call the scan method in $object, which doesn't exist.
Here is a working example of a monitor with callback.
use strict;
use warnings;
use File::Monitor;
my $monitor = File::Monitor->new();
$monitor->watch(
'/tmp/otherfile.txt',
sub {
my ( $name, $event, $change ) = @_;
print "file has been changed\n";
}
);
while(1) {
foreach my $delta ($monitor->scan) {
print $delta->name . " has changed\n";
}
sleep(10);
}
But this depends on polling for changes, which is not ideal.
Can you have your application which creates the data initiate the further processing? This would minimize delay and eliminate the waste of polling.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|