You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if it's a bug or not, but just in case let me provide details:
Get watcher (I downloaded it 09/05/2015)
cd /tmp; git clone https://github.com/splitbrain/Watcher
Create below .ini file:
sudo vim /etc/watcher.ini
[DEFAULT]
logfile=/tmp/watcher.log
pidfile=/tmp/watcher.pid
[job1]
; directory or file to watch. Probably should be abs path.
watch=/tmp/test
events=close
excluded=
recursive=true
autoadd=true
command=ls -l $filename
Create watched dir:
mkdir /tmp/test
Start the daemon and tail life the logs:
cd /tmp/Watcher; ./watcher.py start
tail -F /tmp/watcher.log
Go to the watcher directory and issue a "ls -la" command:
cd /tmp/test; ls -la
Expected behaviour The log shows nothing, since no file was closed (maybe I'm wrong in this assumption...) Found behaviour The daemon starts writing the log without stopping:
Close nowrite: /tmp/test
Close nowrite: /tmp/test
Close nowrite: /tmp/test
Close nowrite: /tmp/test
Close nowrite: /tmp/test
Close nowrite: /tmp/test
Close nowrite: /tmp/test
Close nowrite: /tmp/test
Close nowrite: /tmp/test
Close nowrite: /tmp/test
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
total 0
The text was updated successfully, but these errors were encountered:
Also, if you use multiple bash command, I suggest using && (and-and) instead of ; (semicolon). This way, if one of the commands fails, the remaining commands won't try to run and ruin the system possibly. Or if you want to have a more complex command list, use a bash script and run that with watcher.
My thoughts about your command is that you specified "close" operation to be executed and made the command recursive. Close means any operation that accesses a file and then leaves it. So you basically told watcher to watch the whole test folder in your tmp folder and whenever an application accesses a file and then closes it, the command should be executed. I don't know what is your exact project, but maybe you wish to have a create,modify instead of close as events watched for.
Not sure if it's a bug or not, but just in case let me provide details:
Expected behaviour The log shows nothing, since no file was closed (maybe I'm wrong in this assumption...)
Found behaviour The daemon starts writing the log without stopping:
The text was updated successfully, but these errors were encountered: