On Fri, Aug 13, 2010 at 10:16 AM, Don Delp <nesma...@gmail.com> wrote:
> I didn't think of this, but I bet robocopy sees that the log file is > different from the original when new data is added to it. I don't > know if it does a checksum or just checks the timestamp, but that > would explain the behavior. It sees that your log file is different > and assumes that resuming would corrupt your data. > You are probably right. > If this is the case, you might be back to figuring out how to loop > through the file a few KB at a time. > I don't think this is the answer in your enviroment, but I'll throw it > out there anyway: > > Wget has a resumable download option where it grabs the target file > starting at the point where the local copy leaves off. I'm pretty > sure that it ignores timestamps and etags and only goes by file size. > If you could create a vhost and restrict it to access from localhost, > and use the log folder as the web root, and get the Delorean up to > 88mph, you might be able to get your log. I'll just run "tail -f > other_log_file" and read that one. Oh wait... it is windows so no tail command... Andy -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to nlug-talk@googlegroups.com To unsubscribe from this group, send email to nlug-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
