monitor

I need to monitor a folder and its subdirectories for any file manipulations (add/remove/rename). I've read about FileSystemWatcher but I'd like to monitor changes between each time the program is run or when the user presses the "check for changes" button (FSW seems more orientated to runtime detection). My first thought was to iterate through all the (sub)directories and hash each file. Then, concatenate all the hashes (which have been ordered) and hash that. When I want to check for changes, I repeat the process and check if the hashes are the same. Is this an efficient way of doing it?

I'm running a multithreaded java app in Linux RedHat 5.3 on a machine that has 8 cores (2 quad-core cpu's). I want to monitor the cpu usage of each thread, preferably relative to the maximal cpu it can get (a single thread running on 1 of the cores should go up to 100% and not 12.5%). Can I do it with jconsole/visualVM? Is there another (hopefully free) tool? Yoav If you don't want to use OS specific functions like traversing the /proc directory, you can usually get the values you're looking for from the Java management interface with ThreadMXBean.getThreadCpuTime() and ThreadMXBean

We have many applications running (consider all of them run on Java Platform) and we need to check which ones were used in the last, say, 3 months, and, among those active applications, which parts/functionalities (and how often) are still being used. Is that possible? The goal here is to detect applications or funcionalities which no longer are relevant to the business and remove them, so that we end up having less code to maintain and monitor. Is there any tool which could help us achieving that? We DO use agile methods, so when a new application gets into production it has only the

I want to ask if somebody heard about a SVN monitoring tool for this case: in the past we used MS SourceSafe with checkout & lock mechanism to avoid merges. One benefit of this was the "release manager" can see in the repo whitch files are still not checked in. SVN is a great tool, but sometimes I miss this information, even to avoid big conflicts. Is there a monitoring system which can be used to see who has changed files pending for commiting? On every workstation a service/daemon collecting the modification information, sendig it periodcally to a central server and client apps to see the

http://www.codeproject.com/Articles/28785/Thread-synchronization-Wait-and-Pulse-demystified Queues: The ready queue is the collection of threads that are waiting for a particular lock. The Monitor.Wait methods introduce another queue: the waiting queue. This is required as waiting for a Pulse is distinct from waiting to acquire a lock. Like the ready queue, the waiting queue is FIFO. Recommended pattern: These queues can lead to unexpected behaviour. When a Pulse occurs, the head of the waiting queue is released and is added to the ready queue. However, if there are other threads in the ready