Hello DSpacers,
I came across the checksum checker recently and I don't understand why it is
useful. Here is what I found on the WIKI:-
---
DSpace now comes with a Checksum Checker script (*[dspace]*/bin/checker)
which can be scheduled to verify the checksum of every item within DSpace.
Since DSpace calculates and records the checksum of every file submitted to
it, this script is able to determine whether or not a file has been changed
(either manually or by some sort of corruption or virus).
---
So why would an item be corrupt? Or altered manually? I know that any
filesystem object can get problems when the filesystem goes wobbly, that's
why we have backups. But surely the normal operating system monitoring
utilities will tell us when a filesystem needs repair? Can someone explain
please?
--
Regards,
Andrew M.
http://www.andrewpetermarlow.co.uk
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
