Another important question to ask: what are you doing with what you learned from the test? Nagios? Snmptrap? Zabbix? Grapha? Statd ? Email notification? Smoke signals? I wrote a nagios check once called check_rofs which would write a file read it then delete it and report how that went. Nagios handled telling the right person via the correct means and graphing performance data ( like time to write, time to read, time to unlink.) A system like this has the downside of not checking often enough for some i.e. every 5min by default. I suspect that would be fine for your needs. David David Thornton @northdot9 https://www.quadratic.net On Feb 24, 2017 9:24 PM, "Stewart C. Russell via talk" <talk@gtalug.org> wrote:
On 2017-02-20 12:47 AM, Aruna Hewapathirane wrote:
Hi Stewart, you could just |watch| the file listing (adjusting n seconds to whatever is suitable)
|watch --differences -n 10 ls -l </path/to/shared/dir>|
I hadn't heard of watch before, so thanks! watch *started* to work really well, but then went into a terminal sulk after the FS disappeared during a scan, and refused to show any updates. It's also an interactive program, so doesn't pipe or notify changes in any useful way.
I suspect I'll just have to go with William Park's suggestion of using rsync to a local folder that I have more control over. I still have to correct for the scanner FS's wandering clock, but that's less important.
cheers, Stewart
--- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk