Menu

#244 partial .md5 trashes sharing.cfg

open
nobody
5
2005-09-30
2005-09-30
Mark Goldey
No

If furthur is shut down while it is in the middle of
generating .md5s for each file, then when it restarts,
it chokes reading sharing.cfg, displays an error
message, and then trashes sharing.cfg.

Specifically, this happens if one or more filesets are
complete and queued for .md5 checksum generation. If
there is only one complete download and it is the
download that the .md5 is being generated for, this may
not occur.

First, Furthur reports ""parse error loading
sharing.cfg" and then adds a warning dialog box (which
may be underneath the application window) that gives
the name of the offending fileset:
"jgb1994-11-11.set2.mpg|/shares/jgb1994-11-11.vcdf is
not a valid fileset"

Sharing .cfg looked like this:

[snip]
n="09282005"></l></k>|299336475|d75329b8ce1d37c124d52512c17fc5ea|1081003954674|null|
3
jgb1994-11-11.set2.txt|//shares/gd1970-08-30.vcdf/|15760454a2efab1d41a66982b1b3818f
jgb1994-11-11.set2.md5|/shares/gd1970-08-30.vcdf/|
jgb1994-11-11.set2.mpg|/shares/gd1970-08-30.vcdf/|

Each queued download below that one had all of the file
names listed, but no checksums at all. That's what
Furthur was having trouble with. It simply refused to
read the file and continue the verification process
where it left off. The only way to get back the
filesets was to delete all of the entries for shares
that lacked any checksums (and to adjust the # of
shares at the top of the file).

ListPanel.java contains a class called public
synchronized FileSetInfo getFileSetNeedingMd5() which
is commented with:

// finish any MD5 computations that need done
(including old
// ones that were interrupted when Furthur closed)

Either it doesn't work, or it's never called.

Discussion


Log in to post a comment.

Auth0 Logo