Directory Watch for Windows
Version: 4.0
User Manual
Table of contents
Steve Lohja & Associates
ALL RIGHTS RESERVED
Steve
Lohja
4754
N. Keystone
Email:
slohja@lohja-associates.com
Directory Watch 4.0 for Windows is a directory monitoring application.
This program is ideal in the event you would want to know what is going
on within a directory queue. Directory Watch runs in memory as a background
process surviving the logon/logoff process.
Because of this, you are able to administer the service remotely like
any other MS Windows Service using the Service Control Manager.
You can use Directory Watch to monitor mail server, Print Server, and web
server. In reality, monitor any directory
with files in it.
The file count in a directory is the trigger for Directory Watch
actions. Threshold is the criteria for
the trigger, the number of files in a directory that trigger Directory Watch
actions.
You can monitor up to six directories or execute six actions in any of
these combinations:
Execute up to six different programs.
Send up to six different customizable emails.
Restart up to 18 different MS Windows Services.
Directory Watch can provide a security tool such that to detect a mail
bomb, Worm attack, overflow of a queue or denial of service attack.
Directory Watch does not require a reboot of the computer when installed.
Directory Watch can be used to schedule execution of other programs.
Execute your favorite AntiVirus HD Scan, or signature
Updates. You may execute a batch program
such to FTP files to another location…or check to see if you received the FTP’d files, then run a Directory
Watch Action.
With Directory Watch you can bring workflow and automation into any
process.
You may use the Demo version. But there are limitations. The DEMO is
fully functional for 30 days. When the program expires, it will simply not do
anything but log expiration status to the logs. This software is sold per
server license. Corporate license’s available.
Visit http://www.lohja-associates.com/
to license your copy.
Download http://www.lohja-associates.com/dirwatch/watchdemo.zip.
Extract contents of files into a temporary folder. Execute setup.exe and then
follow the menu prompts.
Directory Watch uses InstallShield and Microsoft Installer.
Directory Watch is also dependent on the Microsoft .NET Framework version
1.1 or greater.
Use the Add/Remove Programs in MS Windows. Then delete any log files generated after the
install.
Directory Watch comes with a Management Console. It is located at c:\program files\lohja\dirwatch\DirectoryWatchConsole.exe
by default.
Directory Watch Service
The service is installed using the “Local System” account. This account only has access to the local
computer Directory Watch is installed on.
If you want to monitor network drives, simply configure the Directory
Watch service to log on as a valid user account with rights to the share.
The service is installed without “Interact with desktop”. The program you execute will never be
displayed on the desktop but can be found in the Task List. Be sure the program you launch terminates
itself at some point or else it will run indefinitely. Be sure the program you launch never waits
for a user response.
When ever making changes in the Directory Watch console, be sure to save
them before closing it. Clicking Start
automatically saves current settings.
When the Service Starts, it reads settings then launches 6 independent
threads. These six independent threads
are queue monitors working independently from each other. At its interval schedule, the queue monitor
will scan the directory. If the
threshold is met, the queue monitor will then execute all actions you have
enabled. After all actions are executed
by queue monitor then it goes to sleep for the Cycles time you have set. When it wakes up again, queue monitor will
load the new settings again and then repeat the steps outlined above for
directory scanning.




Dirwatchx.log
Log file: c:\program files\lohja\dirwatch\Dirwatch1.log. This log file is
not purged every time Directory Watch’s service starts. This file contains
application and directory information. It is a good idea to use this for the
message body when email is enabled. Each
queue has its own log file, dirwatch1, dirwatch2, …,
dirwatch6.
Example dirwatch1.log: