Mailinglist Archive: opensuse (671 mails)

[Per Jessen <per@xxxxxxxxxxxx>]

Gary Hodder wrote:

> Ok md5sum works well but doesnt catch all.
>
> find ./ -type f -print0 | xargs -0 md5sum >> /file.md5
> Then to check
> md5sum -c --quiet /file.md5
> This worked fine no failed files.
>
> There are text files for each mp3 that holds fade times etc, so
> removed a carriage return at the end of one file.
> That file failed checksum on next scan.
> Replaced the carriage return rescanned and all was ok.
>
> So with md5sum a file can be modified then put back to the original
> state before the next scan and md5sum wont pick that up.

Yes, that's true, but then the file hasn't actually changed between your
two checks.  If you want to catch that, mp3info won't help you either,
I think you'll need to monitor the directory/files with inotify() or
some such.  With inotify() you can generate events when the file is
opened for write and/or actually being written to.  I'm not sure if
inotify() can be used from a script though.


/Per

-- 
Per Jessen, Zürich (15.6°C)

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx