I suggest that you should include the dnotify as recommend package because without it the incron command is executed only the first time the file changes, so I have to reload the incron file with incrontab -d root@jarama:~# > log root@jarama:~# incrontab -l /home/losnaranjos/public_html/habitatsoft/500654_UN.TXT IN_MODIFY /root/scripts/scriptnaranjos.sh root@jarama:~# echo /root/scripts/scriptnaranjos.sh #!/bin/bash date >> /home/aarango/log root@jarama:~# echo new >> /home/losnaranjos/public_html/habitatsoft/500654_UN.TXT root@jarama:~# cat /home/aarango/log jue may 20 09:33:00 CEST 2010 root@jarama:~# echo new >> /home/losnaranjos/public_html/habitatsoft/500654_UN.TXT root@jarama:~# cat /home/aarango/log jue may 20 09:33:00 CEST 2010 root@jarama:~# incrontab -d root@jarama:~# echo new >> /home/losnaranjos/public_html/habitatsoft/500654_UN.TXT root@jarama:~# cat /home/aarango/log jue may 20 09:33:00 CEST 2010 jue may 20 09:37:00 CEST 2010 If I install dnotify package it's write twice. Greetings.
tag 582365 + unreproducible thanks Hi Juan, I fail to reproduce your bug with incron 0.5.7 (stable) and incron 0.5.9 (unstable). I've followed the same scenario and it worked perfectly. (keep in mind that when using the symbol IN_MODIFY the file has to exists when saving the incron table. If not, you'll be forced to reload the incrontab (-d option) until the file really exists to get it working). Even if dnotify seems to fix something on your side, it would be a weird workaround. If the bug is reproducible, it has to be fixed in incron itself. Regards, M.