To compile me...

cc checks.c -o checks

-or, if that doesn't work-

gcc checks.c -o checks

This'll leave an executable, called checks, in the folder containing 
the source.  Cool, eh?  You can then copy this to /usr/bin/ if you're 
root, or wherever you put your favorite binaries if you're a regular 
old user.

Then, copy checks.1 into /usr/share/man/man1/ if you're root.  If you're 
a regular old user, throw the manpage wherever you tend to throw your 
manpages.

Whew...that's done!  Now that you have this fine product, I'm sure you're 
asking yourself "Well, Charles, how do I use this dastardly thing?"  Well, 
maybe not quite that, but you know what I mean.  Most of the following 
is a recap of the manpage, so, if you're more inclined to a techical 
reading, go for that.  However, if you want a run-through, this is 
probably a bit easier.

The format for arguments for checks 0.3.x is:

	checks [-ms time in minutes or seconds] [-n] [-p] [directories...]

So how does this break down?  Well, if you want checks to check a folder 
every 75 seconds, you'd type in something like:

	checks -s 75 ~/lala/

It'll look every 75 seconds to see if anything's changed in ~/lala .  
You can do the same for minutes, only changing -s to -m.  If you want 
to check multiples, just list multiple directories like:

	checks -m 3 ~/Supergrass/ ~/tonight/

Now let's try something really different.  Say you only want checks 
to alert you when you get a new file in a folder, but want it silent 
when you're deleting old stuff from the folder (assume you would name 
a folder something so atrocious).  This does the trick:

	checks -n ~/in_it_for_the_money/

Thus, this would check both of those folders every three minutes.  Now, 
I'm sure you're asking yourself "What the heck is -p?"  Well, maybe not 
quite that, but you know what I mean.  If you enter:

	checks -m 2 -p

checks will check the folders listed in ~/.checksrc , if such a file 
exists, every 2 minutes.  If it doesn't exist, well, checks'll warn you.

Why use a .checksrc?  Well the folder or folders you list 
in it have their values stored between logout/login, so you can see if there 
have been changes, even if checks wasn't running.  A sample .checksrc is
included with the package, named dot.checksrc .  You can edit the folders 
listed therein and copy it to your home directory.  Name it .checksrc   
Now, when you start checks with the -p argument, it will check the 
folders in the .checksrc, and will report if there've been any changes 
since you last ran checks.

If you want to edit your previously created .checksrc, first quit checks 
to avoid any wierdness.  All you'll then need to do is add another line 
with the path to the folder you'd like to check, or remove the line of a 
folder you don't want checks to check.  Simple, no?

If you're horribly confused still:
*	If the command line arguments are confusing you, try the 
	manpage, where I may have been a tad more coherent.  Try 
	some random stabs at the argument you think should work.  
	checks will give you help if it's confused.
*	If the .checksrc file confuses you, open the template file and 
	read the info therein.  That will show you how checks expects the 
	file to be put together.
*	Curious if there's a new version?  My software site is:
		http://www.diablonet.net/~mercadal/
*	If you get errors compiling, unexpected errors while running, 
	an itching, burning sensation during exectuion, or 
	anything that it doesn't seem I've covered anywhere, contact 
	me via e-mail:
		charleschuck@mac.com

Enjoy!  Hopefully you can find this useful!
