Comments on: Recursive Inotify Daemon

By: BFallert

BFallert — Wed, 18 Mar 2015 14:36:20 +0000

for IN_DELETE and IN_MOVED_FROM you can use following change.

if(-d $filename && $e->IN_CREATE) {
create_watcher($inotify, $filename);
return
}
elsif($e->IN_DELETE) {
print __LINE__ . “: IN_DELETE $filename\n”;
}
elsif($e->IN_MOVED_FROM){
print “IN_MOVE_FROM $filename\n”
}
elsif(-f $filename){
if($e->IN_CLOSE_WRITE){
print “IN_CLOSE_WRITE $filename\n”
}
#elsif($e->IN_MOVED_FROM){
# print “IN_MOVE_FROM $filename\n”
#}
elsif($e->IN_MOVED_TO){
print “IN_MOVED_TO $filename\n”
}
#elsif($e->IN_DELETE){
# print “IN_DELETE $filename\n”
#}
}

By: Marcos Athanasoulis

Marcos Athanasoulis — Thu, 29 Jan 2015 08:06:00 +0000

This does not seem to be detecting deletion of files or directories (as noted in other comments), seems like the code should be working for that. Has anyone gotten this to work for deletion? It is working great for creates…

By: Jack Nond

Jack Nond — Mon, 22 Sep 2014 14:12:27 +0000

Here’s is a another simple watcher for directory trees: https://metacpan.org/pod/AnyEvent::Inotify::Simple#METHODS

It can easily be extended to watch deletion of file and folders too.

By: Cory Albrecht

Cory Albrecht — Fri, 19 Sep 2014 05:44:13 +0000

The -f check you do for the IN_DELETE and IN_MOVED_FROM will not work because at that point (firing of the inotify2 event) that pathname no longer exists. Your example daemon will never print out those two notices.

Also, you don’t remove any watchers when a directory is deleted. 🙂

By: Yiorgos Stamoulis

Yiorgos Stamoulis — Thu, 23 Jan 2014 09:37:09 +0000

Hi Johnny,

this is great, it work like a charm 🙂

A small change you may consider:

> use File::Basename;
> my $basename = basename($0);
> my $PID_FILE = “/var/run/$basename.pid”;

otherwise it won’t start unless you are in the same directory as the script itself

(I have added a init script an run it as a daemon at system startup)

Best Regards

Yiorgos

By: Junaid

Junaid — Mon, 21 Oct 2013 12:29:57 +0000

Hi there, First of all please accept my huge gratitude for providing this script, it is a great help and i was looking for something like this very desperately.
But as I haven’t used perl before so i need your help regarding the error message i receive, when I try to invoke the script.
It says:
” Can’t locate AnyEvent.pm in @INC (@INC contains: /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at notifier.perl line 6.
BEGIN failed–compilation aborted at notifier.perl line 6.”
What do i need to do to fix this problem.
Secondly i wanted further help regarding
1. How to add more events. like “File modification event”
2. Connecting this script to a postgresql data for logging the events with corresponding timestamp to the database.

Many thanks once again for all the help.

Cheers,

Malik Junaid

By: Sarakenidis Nikos

Sarakenidis Nikos — Wed, 07 Nov 2012 15:38:48 +0000

It was 8192 in one of my ubuntu servers here.. I need >250000

By: Johnny Morano

Johnny Morano — Wed, 07 Nov 2012 15:13:29 +0000

In reply to Sarakenidis Nikos.

Cool! It must be really huge then, cause overhere it is set by default to 65536:

# cat /proc/sys/fs/inotify/max_user_watches
65536

Cheers!

By: Sarakenidis Nikos

Sarakenidis Nikos — Wed, 07 Nov 2012 14:06:42 +0000

In reply to Sarakenidis Nikos.

OK I’ve changed /proc/sys/fs/inotify/max_user_watches
and everything works as expected. My bad!

Cheers

By: Sarakenidis Nikos

Sarakenidis Nikos — Wed, 07 Nov 2012 13:30:23 +0000

In reply to Johnny Morano.

1. touch /data/vault/testfile
2. mkdir -p /data/vault/testdir
3. touch /data/vault/testdir/testfile

IN_CLOSE_WRITE /data/vault/testfile
Watching /data/vault/testdir

Third command does not produce any output

Is there a limit to the number of subdirectories inotify can watch? Cause mine is huge. Maybe that’s the problem.