Re: Re: Re: Storing program settings and state

Suppose you have a 7Gb file and a link that goes down after 20 seconds.

I'd look into getting the link fixed.

obviously Unix-only is not of interest to me

I'm sure rsync will run on Windows, at least in a cygwin environment. (I wouldn't be surprised if there were a native port.)

Finally, I agree with Corion's assessment that all of the needed information should be in the files themselves. There should be no reason to write metadata elsewhere.

-sauoq
"My two cents aren't worth a dime.";

Comment on Re: Re: Re: Storing program settings and state

Replies are listed 'Best First'.
Re: Re: Re: Re: Storing program settings and state by John M. Dlugosz (Monsignor) on Jul 10, 2003 at 03:16 UTC
After starting into the rsync paper, I see why y'all are not seeing my problem. This is not two peers that can compare notes. It is ONE computer and a remote storage system. Reading the file to compare it is just as problematic as copying it! In particular, I'm trying to get files off a Maxstore FireWire enclosure. It transfers a while and then has to have power cycled.	[reply]
"Re: "x5 . "Storing program settings and state" by revdiablo (Prior) on Jul 10, 2003 at 19:00 UTC
Hmm. Sounds like that remote storage system is horribly broken. You still shouldn't necessarily need a metadata file storing how many bytes you've received -- just look at the file you've got. Count how many bytes it has, and skip that many. This is probably error-prone, but hopefully better than nothing. In any case, I assume you are able to tell the remote store to skip some amount of bytes before starting the transfer back up, right? If not... I'm not sure how you would accomplish this.	[reply]
Re: "Re: "x5 . "Storing program settings and state" by John M. Dlugosz (Monsignor) on Jul 11, 2003 at 05:47 UTC
just look at the file you've got. Count how many bytes it has, I want to support multiple passes, to make sure it was read the first time. That is, "verify" won't see a short file, but the whole file size. Also, I want to be able to allocate the entire file size ahead of time, to make sure it fits in the destination. I assume you are able to tell the remote store to skip some amount of bytes before starting the transfer back up, right? Right, just `seek`. —John	[reply] [d/l]