diff -Nru iwatch-0.2.2/debian/changelog iwatch-0.2.2/debian/changelog --- iwatch-0.2.2/debian/changelog 2016-10-23 22:23:02.000000000 +0000 +++ iwatch-0.2.2/debian/changelog 2017-11-11 22:00:53.000000000 +0000 @@ -1,3 +1,14 @@ +iwatch (0.2.2-5) unstable; urgency=medium + + * debian/control: + - Bumped Standards-Version to 4.1.1. + - Little fixes in long description. + * debian/copyright: updated packaging copyright years. + * debian/manpage/: updated the manpage and fixed some issues. + * debian/watch: improved. + + -- Joao Eriberto Mota Filho Sat, 11 Nov 2017 20:00:53 -0200 + iwatch (0.2.2-4) unstable; urgency=medium * Bumped DH level to 10. diff -Nru iwatch-0.2.2/debian/control iwatch-0.2.2/debian/control --- iwatch-0.2.2/debian/control 2016-10-23 22:09:35.000000000 +0000 +++ iwatch-0.2.2/debian/control 2017-11-11 22:00:53.000000000 +0000 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Joao Eriberto Mota Filho Build-Depends: debhelper (>= 10) -Standards-Version: 3.9.8 +Standards-Version: 4.1.1 Homepage: http://iwatch.sf.net Vcs-git: https://anonscm.debian.org/git/collab-maint/iwatch.git Vcs-Browser: https://anonscm.debian.org/git/collab-maint/iwatch.git @@ -34,7 +34,7 @@ . - Send notifications via email about changes. - Take programmable actions immediately, as emit alerts via - XMPP (jabber) messages, WhatsApp or execute a local program + XMPP (jabber) messengers, WhatsApp or execute a local program or script. - Act as HIDS (Host-based Intrusion Detection System) or an integrity checker, complementing the firewall system in @@ -47,4 +47,4 @@ insertions. Other example is to synchronize configuration files between machines, when they are changed, as in DHCP servers acting in failover mode. You also use to synchronize files, via rsync - when these files when changed. + when these files are changed. diff -Nru iwatch-0.2.2/debian/copyright iwatch-0.2.2/debian/copyright --- iwatch-0.2.2/debian/copyright 2016-10-22 21:02:14.000000000 +0000 +++ iwatch-0.2.2/debian/copyright 2017-11-11 22:00:53.000000000 +0000 @@ -8,7 +8,7 @@ Files: debian/* Copyright: 2006-2012 Michael Prokop - 2014-2016 Joao Eriberto Mota Filho + 2014-2017 Joao Eriberto Mota Filho License: GPL-2+ License: GPL-2 or GPL-2+ diff -Nru iwatch-0.2.2/debian/manpage/create-man.sh iwatch-0.2.2/debian/manpage/create-man.sh --- iwatch-0.2.2/debian/manpage/create-man.sh 2016-10-23 21:52:40.000000000 +0000 +++ iwatch-0.2.2/debian/manpage/create-man.sh 2017-11-11 22:00:53.000000000 +0000 @@ -3,7 +3,7 @@ # by Eriberto # Create the manpage using txt2man command. -T2M_DATE="14 Jun 2014" +T2M_DATE="11 Nov 2017" T2M_NAME=iwatch T2M_VERSION=0.2.2 T2M_LEVEL=1 diff -Nru iwatch-0.2.2/debian/manpage/iwatch.1 iwatch-0.2.2/debian/manpage/iwatch.1 --- iwatch-0.2.2/debian/manpage/iwatch.1 2016-10-23 21:54:37.000000000 +0000 +++ iwatch-0.2.2/debian/manpage/iwatch.1 2017-11-11 22:00:53.000000000 +0000 @@ -1,5 +1,5 @@ .\" Text automatically generated by txt2man -.TH iwatch 1 "14 Jun 2014" "iwatch-0.2.2" "realtime filesystem monitoring program using inotify" +.TH iwatch 1 "11 Nov 2017" "iwatch-0.2.2" "realtime filesystem monitoring program using inotify" .SH NAME \fBiwatch \fP- realtime filesystem monitoring program using inotify \fB @@ -16,17 +16,21 @@ .fam T .fi .SH DESCRIPTION -inotify (inode notify) is a Linux kernel subsystem that monitors events in filesystems and reports those events to applications in real time. +inotify (inode notify) is a Linux kernel subsystem that monitors events in filesystems and reports those events to +applications in real time. .PP -inotify can be used to monitor individual files or directories. When a directory is monitored, inotify will return events for the directory -itself, and for files inside this directory. The inotify support was added to Linux Kernel 2.6.13. +inotify can be used to monitor individual files or directories. When a directory is monitored, inotify will return +events for the directory itself, and for files inside this directory. The inotify support was added to Linux Kernel 2.6.13. .PP -iWatch is a Perl wrap to inotify to monitor changes in specific directories or files, sending alarm to the system administrator in real time. It can: +Do not forget to consider directories \fIas\fP "special files". See more details at http://www.tldp.org/LDP/intro-linux/html/sect_03_01.html +.PP +iWatch is a Perl wrap to inotify to monitor changes in specific directories or files, sending alarms to the system +administrator in real time. So, iWatch can do: .RS .IP \(bu 3 Send notifications via email about changes. .IP \(bu 3 -Take programmable actions immediately, \fIas\fP emit alerts via XMPP messages, WhatsApp or execute a local program or script. +Take programmable actions immediately, \fIas\fP emit alerts via XMPP messengers, WhatsApp or execute a local program or script. .IP \(bu 3 Act \fIas\fP HIDS (Host-based Intrusion Detection System) or an integrity checker, complementing the local firewall systems. .RE @@ -42,13 +46,17 @@ to disable email notification, and instead setup a \fIcommand\fP to be executed if an event occurs. Per default iWatch only monitor following events: close_write, create, delete, move, delete_self and move_self. But you can specify any possible events, like access, attrib, modify or all_events. See the EVENTS section for more details. +.PP +A good example of iWatch usage is to monitor the pages directory in webservers to notify, in real time, about defacements +or file insertions. Other example is to synchronize configuration files between machines, when they are changed, \fIas\fP in +DHCP servers acting in failover mode. You also use to synchronize files, via rsync when these files are changed. .SH OPTIONS Usage for daemon mode (background) of iWatch: .RS .TP .B \fB-d\fP -Execute the application \fIas\fP daemon. iWatch will run in foregroud without this option. +Execute the application \fIas\fP daemon. iWatch will run in foreground without this option. .TP .B \fB-f\fP @@ -68,7 +76,8 @@ .TP .B \fB-c\fP <\fIcommand\fP> -You can specify a \fIcommand\fP to be executed if an event occurs. For details about the available strings, take a look at STRINGS FOR COMMAND section. +You can specify a \fIcommand\fP to be executed if an event occurs. For details about the available strings, +take a look at STRINGS FOR COMMAND section. .TP .B \fB-C\fP <\fIcharset\fP> @@ -76,7 +85,8 @@ .TP .B \fB-e\fP -Specify a list of events that you want to watch. For details about possible events, take a look at EVENTS section. +Specify a list of events that you want to watch. For details about possible events, take +a look at EVENTS section. .TP .B \fB-h\fP, \fB--help\fP @@ -120,7 +130,7 @@ .B \fB-X\fP Similar to \fB-x\fP but specifying a regex \fIstring\fP \fIas\fP \fIexception\fP. -.SH STRINGS FOR COMMAND +.SH STRINGS FOR COMMANDS When using the '\fB-c\fP <\fIcommand\fP>' option, these strings will be available: .TP .B @@ -129,11 +139,11 @@ .TP .B %e -Event name. +Event name. (e.g.: IN_CLOSE_WRITE) .TP .B %f -Full path of the filename that gets an event. +Full path of the filename that gets an event. (e.g.: /var/www/index.html) .TP .B %F @@ -141,45 +151,45 @@ .TP .B %p -Program name (iWatch). +Program name, always "iWatch". .TP .B %v -Version number. +Version number. (e.g.: 0.2.2) .SH EVENTS Following are the possible events you can use with the '\fB-e\fP' option: .TP .B access -file was accessed. +file/directory was accessed. .TP .B attrib -file attributes changed. +file/directory attributes changed. .TP .B close -file closed, regardless of read/write mode. +file/directory closed, regardless of read/write mode. .TP .B close_nowrite -file closed, after being opened in read-only mode. +file/directory closed, after being opened in read-only mode. .TP .B close_write -file closed, after being opened in writeable mode. +file/directory closed, after being opened in writable mode. .TP .B create -a file was created within watched directory. +a file/directory was created within watched directory. .TP .B delete -a file was deleted within watched directory. +a file/directory was deleted within watched directory. .TP .B delete_self -the watched file was deleted. +the watched file/directory was deleted. .TP .B ignored @@ -187,23 +197,23 @@ .TP .B isdir -event occurred against dir. +event occurred against a directory. .TP .B modify -file was modified. +a file content was modified. .TP .B move -a file/dir within watched directory was moved. +a file/directory within watched directory was moved. .TP .B moved_from -file was moved away from. +a file was moved away from. .TP .B moved_to -file was moved to. +a file was moved to. .TP .B oneshot @@ -211,7 +221,7 @@ .TP .B open -file was opened. +a file/directory was opened. .TP .B q_overflow @@ -227,24 +237,24 @@ .TP .B all_events -all events. +all possible events. .SH COMMAND LINE USAGE EXAMPLES .TP .B $ \fBiwatch\fP /tmp -Monitor changes in /tmp directory with default events. +Monitor changes in /tmp directory, using default events, without recursivity. .TP .B $ \fBiwatch\fP \fB-r\fP \fB-e\fP access,create \fB-m\fP root@example.com \fB-x\fP /etc/mail /etc Monitor only access and create events in /etc directory, recursively, with /etc/mail \fIas\fP \fIexception\fP, and send email -notification to root@example.com. +notification to root@example.com if a listed event occurs. .TP .B -$ \fBiwatch\fP \fB-r\fP \fB-c\fP (w;ps \fB-ef\fP)|mail \fB-s\fP '%f was changed' root@localhost /bin -Monitor /bin directory, recursively, and execute the commands 'w' and 'ps \fB-ef\fP', +$ \fBiwatch\fP \fB-r\fP \fB-c\fP '(w; ps \fB-aux\fP)' | mail \fB-s\fP '%f was changed' root@localhost /bin +Monitor /bin directory, recursively, and execute the commands 'w' and 'ps \fB-aux\fP', sending the results to root@localhost, using ' was changed' \fIas\fP subject. -To see about '%f' take a look at STRINGS FOR COMMAND section. +To see about '%f' take a look at STRINGS FOR COMMANDS section. .TP .B $ \fBiwatch\fP \fB-r\fP \fB-X\fP '.svn' ~/projects @@ -263,7 +273,7 @@ WEB server integrity monitoring - /var/www + /var/www /var/www/counter @@ -280,16 +290,18 @@ .PP The place can have several blocks. Inside these blocks (), the space is used to add a title that will identify the -purpose of the block. The 'contactpoint' line contains the destination email address (To:) and name -when sending notifications by email. +purpose of the block. This field is a visual text to indicate what the block does. The +does nothing. It is a tag for people reading the configuration file. The 'contactpoint' line contains +the destination email address (To:) and name when sending notifications by email. .PP Each line can monitor a file/directory and execute actions. The first path line showed will monitor recursively the directory /var/www. As no events was defined, iWatch will employ the default event (close_write, create, delete, move, delete_self and move_self events). If an event -occurs, the syslog will register it and a message reporting the program name (%p = iWatch), the event +occurs, the syslog will not register it and a message reporting the program name (%p = iWatch), the event (%e) and the monitored file/directory name (%f) will be sent via XMPP protocol (sendxmpp external -program) to foo@jabber-br.org. Note that alert="off" will disable any sending email. Another important -point is that a second line is excluding the /var/www/counter file/directory from observation. +program) to foo@jabber-br.org. Note that alert="off" will disable any sending email. Other way to avoid +an email message is drop the line "contactpoint". Another important point is that a second line is +excluding the /var/www/counter file/directory from observation. .PP The showed example uses the sendxmpp \fIcommand\fP. Other good possibility is to apply the yowsup-cli \fIcommand\fP to send WhatsApp messages. @@ -307,44 +319,45 @@ Public Website /var/www/localhost/htdocs - /var/www/localhost/htdocs/About /var/www/localhost/htdocs/Photos Operating System /etc/apache2 - /etc/passwd /etc/mail /etc/mail/statistics /etc - Only Test + Only a test - /tmp/dir1 - /tmp/dir2 - /tmp/dir3 - /tmp/dir4 + /tmp/dir1 + /tmp/dir2 + /tmp/dir3 + /tmp/dir4 .fam T .fi -The first block monitors a directories and has special actions for two files but no execute a \fIcommand\fP in neither of them. -The first path is a single (non recursive) directory /var/www/localhost/htdocs and any notification will be sent to the contact point -webmaster@example.com. Note that have no events specified. So, the default (close_write, create, delete, move, delete_self -and move_self) will be used. The second path is the file /var/www/localhost/htdocs/About. This file is inside the last directory. -The difference is that all activities over this file will be logged in /var/log/syslog. The third path will monitor, recursively, -the directory /var/www/localhost/htdocs/Photos (also inside of the first directory). No log. Default events will be notified via mail. -.PP -The second block has five monitoring. All notification will be sent to admin@localhost. The main novelty over the first block -is that a path uses a 'filter' instruction to watch /etc/shadow and /etc/passwd at the same time. To understand better this -situation, see the '\fB-t\fP' in OPTIONS section. -.PP -The last block monitors a default event in first line and several non default events in the following three lines. In all lines the 'alert' -is defined \fIas\fP 'off'. So, iWatch will not send emails using the builtin mail engine. However, in three lines the external \fIcommand\fP 'mail' -was used to send personalized emails. +The first block monitors a directory and has special actions for a file but no execute a \fIcommand\fP for it. +The first path is a single (non recursive) directory /var/www/localhost/htdocs and any notification will be sent to +the contact point webmaster@example.com. Note that have no events specified. So, the default events (close_write, +.TP +.B +create, delete, move, delete_self +and move_self) will be used. The second path will monitor, recursively, the +directory /var/www/localhost/htdocs/Photos (also inside of the first directory). Default events will be notified +via mail. +.PP +The second block has four monitoring. All notification will be sent to admin@localhost. The main novelty over the +first block is that a path uses a 'filter' instruction to watch /etc/shadow and /etc/passwd at the same time. To +understand better this situation, see the '\fB-t\fP' at OPTIONS section. +.PP +The last block monitors default events in first line and several non default events in the following three lines. +In several lines the 'alert' is defined \fIas\fP 'off'. So, iWatch will not send emails using the builtin mail engine. +However, in three lines the external \fIcommand\fP 'mail' was used to send personalized emails. .SH LEARNING ABOUT EVENTS A tip to learn about events is watch the iWatch \fIcommand\fP executing with '\fB-e\fP all_events' option. The following example will monitor a 'ls /tmp' \fIcommand\fP. @@ -415,8 +428,8 @@ .fam T .fi .SH SEE ALSO -\fBsendxmpp\fP(1), \fByowsup-cli\fP(1) +\fBinotify\fP(7), \fBsendxmpp\fP(1), \fByowsup-cli\fP(1) .SH AUTHOR iWatch was written by Cahya Wirawan . .PP -This manual page was written by Michael Prokop and was updated/improved by Joao Eriberto Mota Filho for the Debian project (but may be used by others). +This manual page was written by Michael Prokop and was updated/expanded by Joao Eriberto Mota Filho for the Debian project (but may be used by others). diff -Nru iwatch-0.2.2/debian/manpage/iwatch.txt iwatch-0.2.2/debian/manpage/iwatch.txt --- iwatch-0.2.2/debian/manpage/iwatch.txt 2016-10-23 21:54:34.000000000 +0000 +++ iwatch-0.2.2/debian/manpage/iwatch.txt 2017-11-11 22:00:53.000000000 +0000 @@ -8,15 +8,19 @@ [-X ] DESCRIPTION - inotify (inode notify) is a Linux kernel subsystem that monitors events in filesystems and reports those events to applications in real time. + inotify (inode notify) is a Linux kernel subsystem that monitors events in filesystems and reports those events to + applications in real time. - inotify can be used to monitor individual files or directories. When a directory is monitored, inotify will return events for the directory - itself, and for files inside this directory. The inotify support was added to Linux Kernel 2.6.13. + inotify can be used to monitor individual files or directories. When a directory is monitored, inotify will return + events for the directory itself, and for files inside this directory. The inotify support was added to Linux Kernel 2.6.13. - iWatch is a Perl wrap to inotify to monitor changes in specific directories or files, sending alarm to the system administrator in real time. It can: + Do not forget to consider directories as "special files". See more details at http://www.tldp.org/LDP/intro-linux/html/sect_03_01.html + + iWatch is a Perl wrap to inotify to monitor changes in specific directories or files, sending alarms to the system + administrator in real time. So, iWatch can do: - Send notifications via email about changes. - - Take programmable actions immediately, as emit alerts via XMPP messages, WhatsApp or execute a local program or script. + - Take programmable actions immediately, as emit alerts via XMPP messengers, WhatsApp or execute a local program or script. - Act as HIDS (Host-based Intrusion Detection System) or an integrity checker, complementing the local firewall systems. iWatch can run as daemon, as well a simple command. The daemon mode uses a XML configuration file, and put a list @@ -31,17 +35,23 @@ monitor following events: close_write, create, delete, move, delete_self and move_self. But you can specify any possible events, like access, attrib, modify or all_events. See the EVENTS section for more details. + A good example of iWatch usage is to monitor the pages directory in webservers to notify, in real time, about defacements + or file insertions. Other example is to synchronize configuration files between machines, when they are changed, as in + DHCP servers acting in failover mode. You also use to synchronize files, via rsync when these files are changed. + OPTIONS Usage for daemon mode (background) of iWatch: - -d Execute the application as daemon. iWatch will run in foregroud without this option. + -d Execute the application as daemon. iWatch will run in foreground without this option. -f Specify alternative configuration file. Default is /etc/iwatch/iwatch.xml. -p Specify an alternate pid file. Default: /var/run/iwatch.pid. -v Be verbose. Usage for command line mode (foreground) of iWatch: - -c You can specify a command to be executed if an event occurs. For details about the available strings, take a look at STRINGS FOR COMMAND section. + -c You can specify a command to be executed if an event occurs. For details about the available strings, + take a look at STRINGS FOR COMMAND section. -C Specify the charset (default is utf-8). - -e Specify a list of events that you want to watch. For details about possible events, take a look at EVENTS section. + -e Specify a list of events that you want to watch. For details about possible events, take + a look at EVENTS section. -h, --help Print help message. -m Contact point's email address. Without this option, iWatch will not send any email notification. -r Recursivity when watching a directory. @@ -59,48 +69,48 @@ -x Specify the file or directory which should not be watched. -X Similar to -x but specifying a regex string as exception. -STRINGS FOR COMMAND +STRINGS FOR COMMANDS When using the '-c ' option, these strings will be available: %c Event cookie number. - %e Event name. - %f Full path of the filename that gets an event. + %e Event name. (e.g.: IN_CLOSE_WRITE) + %f Full path of the filename that gets an event. (e.g.: /var/www/index.html) %F The old filename in case moved_to event. - %p Program name (iWatch). - %v Version number. + %p Program name, always "iWatch". + %v Version number. (e.g.: 0.2.2) EVENTS Following are the possible events you can use with the '-e' option: - access file was accessed. - attrib file attributes changed. - close file closed, regardless of read/write mode. - close_nowrite file closed, after being opened in read-only mode. - close_write file closed, after being opened in writeable mode. - create a file was created within watched directory. - delete a file was deleted within watched directory. - delete_self the watched file was deleted. + access file/directory was accessed. + attrib file/directory attributes changed. + close file/directory closed, regardless of read/write mode. + close_nowrite file/directory closed, after being opened in read-only mode. + close_write file/directory closed, after being opened in writable mode. + create a file/directory was created within watched directory. + delete a file/directory was deleted within watched directory. + delete_self the watched file/directory was deleted. ignored file was ignored. - isdir event occurred against dir. - modify file was modified. - move a file/dir within watched directory was moved. - moved_from file was moved away from. - moved_to file was moved to. + isdir event occurred against a directory. + modify a file content was modified. + move a file/directory within watched directory was moved. + moved_from a file was moved away from. + moved_to a file was moved to. oneshot only send event once. - open file was opened. + open a file/directory was opened. q_overflow event queued overflowed. unmount file system on which watched file exists was unmounted. default close_write, create, delete, move, delete_self and move_self. - all_events all events. + all_events all possible events. COMMAND LINE USAGE EXAMPLES - $ iwatch /tmp Monitor changes in /tmp directory with default events. + $ iwatch /tmp Monitor changes in /tmp directory, using default events, without recursivity. $ iwatch -r -e access,create -m root@example.com -x /etc/mail /etc Monitor only access and create events in /etc directory, recursively, with /etc/mail as exception, and send email - notification to root@example.com. + notification to root@example.com if a listed event occurs. - $ iwatch -r -c (w;ps -ef)|mail -s '%f was changed' root@localhost /bin Monitor /bin directory, recursively, and execute the commands 'w' and 'ps -ef', + $ iwatch -r -c '(w; ps -aux)' | mail -s '%f was changed' root@localhost /bin Monitor /bin directory, recursively, and execute the commands 'w' and 'ps -aux', sending the results to root@localhost, using ' was changed' as subject. - To see about '%f' take a look at STRINGS FOR COMMAND section. + To see about '%f' take a look at STRINGS FOR COMMANDS section. $ iwatch -r -X '.svn' ~/projects Monitor ~/projects directory, recursively, but exclude any .svn directories inside. This cannot be done with a normal '-x' option since '-x' can only exclude the defined path. @@ -116,7 +126,7 @@ WEB server integrity monitoring - /var/www + /var/www /var/www/counter @@ -131,16 +141,18 @@ The place can have several blocks. Inside these blocks (), the space is used to add a title that will identify the - purpose of the block. The 'contactpoint' line contains the destination email address (To:) and name - when sending notifications by email. + purpose of the block. This field is a visual text to indicate what the block does. The + does nothing. It is a tag for people reading the configuration file. The 'contactpoint' line contains + the destination email address (To:) and name when sending notifications by email. Each line can monitor a file/directory and execute actions. The first path line showed will monitor recursively the directory /var/www. As no events was defined, iWatch will employ the default event (close_write, create, delete, move, delete_self and move_self events). If an event - occurs, the syslog will register it and a message reporting the program name (%p = iWatch), the event + occurs, the syslog will not register it and a message reporting the program name (%p = iWatch), the event (%e) and the monitored file/directory name (%f) will be sent via XMPP protocol (sendxmpp external - program) to foo@jabber-br.org. Note that alert="off" will disable any sending email. Another important - point is that a second line is excluding the /var/www/counter file/directory from observation. + program) to foo@jabber-br.org. Note that alert="off" will disable any sending email. Other way to avoid + an email message is drop the line "contactpoint". Another important point is that a second line is + excluding the /var/www/counter file/directory from observation. The showed example uses the sendxmpp command. Other good possibility is to apply the yowsup-cli command to send WhatsApp messages. @@ -156,42 +168,40 @@ Public Website /var/www/localhost/htdocs - /var/www/localhost/htdocs/About /var/www/localhost/htdocs/Photos Operating System /etc/apache2 - /etc/passwd /etc/mail /etc/mail/statistics /etc - Only Test + Only a test - /tmp/dir1 - /tmp/dir2 - /tmp/dir3 - /tmp/dir4 + /tmp/dir1 + /tmp/dir2 + /tmp/dir3 + /tmp/dir4 - The first block monitors a directories and has special actions for two files but no execute a command in neither of them. - The first path is a single (non recursive) directory /var/www/localhost/htdocs and any notification will be sent to the contact point - webmaster@example.com. Note that have no events specified. So, the default (close_write, create, delete, move, delete_self - and move_self) will be used. The second path is the file /var/www/localhost/htdocs/About. This file is inside the last directory. - The difference is that all activities over this file will be logged in /var/log/syslog. The third path will monitor, recursively, - the directory /var/www/localhost/htdocs/Photos (also inside of the first directory). No log. Default events will be notified via mail. - - The second block has five monitoring. All notification will be sent to admin@localhost. The main novelty over the first block - is that a path uses a 'filter' instruction to watch /etc/shadow and /etc/passwd at the same time. To understand better this - situation, see the '-t' in OPTIONS section. - - The last block monitors a default event in first line and several non default events in the following three lines. In all lines the 'alert' - is defined as 'off'. So, iWatch will not send emails using the builtin mail engine. However, in three lines the external command 'mail' - was used to send personalized emails. + The first block monitors a directory and has special actions for a file but no execute a command for it. + The first path is a single (non recursive) directory /var/www/localhost/htdocs and any notification will be sent to + the contact point webmaster@example.com. Note that have no events specified. So, the default events (close_write, + create, delete, move, delete_self and move_self) will be used. The second path will monitor, recursively, the + directory /var/www/localhost/htdocs/Photos (also inside of the first directory). Default events will be notified + via mail. + + The second block has four monitoring. All notification will be sent to admin@localhost. The main novelty over the + first block is that a path uses a 'filter' instruction to watch /etc/shadow and /etc/passwd at the same time. To + understand better this situation, see the '-t' at OPTIONS section. + + The last block monitors default events in first line and several non default events in the following three lines. + In several lines the 'alert' is defined as 'off'. So, iWatch will not send emails using the builtin mail engine. + However, in three lines the external command 'mail' was used to send personalized emails. LEARNING ABOUT EVENTS A tip to learn about events is watch the iWatch command executing with '-e all_events' option. The following example @@ -248,9 +258,9 @@ syslog (on|off) "off" SEE ALSO - sendxmpp(1), yowsup-cli(1) + inotify(7), sendxmpp(1), yowsup-cli(1) AUTHOR iWatch was written by Cahya Wirawan . - This manual page was written by Michael Prokop and was updated/improved by Joao Eriberto Mota Filho for the Debian project (but may be used by others). + This manual page was written by Michael Prokop and was updated/expanded by Joao Eriberto Mota Filho for the Debian project (but may be used by others). diff -Nru iwatch-0.2.2/debian/watch iwatch-0.2.2/debian/watch --- iwatch-0.2.2/debian/watch 2016-10-23 21:57:30.000000000 +0000 +++ iwatch-0.2.2/debian/watch 2017-11-11 22:00:53.000000000 +0000 @@ -1,2 +1,2 @@ version=4 -http://sf.net/iwatch/iwatch-(\d\S+)\.(?:tgz|tar)(?:\.bz2|\.gz|\.xz)? +http://sf.net/iwatch/iwatch-(\d\S+)\.(?:tgz|tar\.(?:bz2|gz|xz))?