General Topics

DiskTester

MemoryTester

IntegrityChecker

dgl

Tips and How-To

Troubleshooting

Tips

This pages offers some suggestions for using IntegrityChecker.

The .ic file and web servers

IntegrityChecker creates its “.ic” file in every folder that you update. This file contains file names, dates and sizes.

To be clear, “security by obscurity” (not having the ".ic" file) is not security. Anything sensitive on your server should be properly protected with access controls.

GUI tips

Selecting more than one item to process

You can select more than one folder at a time:

img
Selecting more than one folder

Command line tips

Volume name

You do not need to use /Volumes/Name for a volume eg the following are equivalent:

ic verify /Volumes/Master
ic verify Master

Multi-path

You can specify any number of paths for verify/update-*/status/clean.

or example, three volumes and ~/Library are specified here:

ic verify Master Backup1 Backup2 /Users/lloyd/Library

Performance

If you want to process more than one volume at a time (which are on distinct physical drives), running them in parallel is much faster than in one pass, because processing speed is almost always limited by disk speed. Therefore, more than one 'ic' can run in parallel with plenty of CPU power available.

This approach is the slowest, because the files are dealt with in order:

ic verify Master Backup1 Backup2 MyDVD

Instead, invoke a separate ic for each volume, each in a separate Terminal window. Each ic can then run on its own in parallel with the others:

ic verify Master
ic verify Backup1
ic verify Backup2
ic verify MyDVD

Previous page: Hashes, Speed, etc
Next page: verify