Other than the "--ignore-length" option I mentioned previously, no. Sorry.
Mark Post -----Original Message----- From: Preston [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: -N option Aaron S. Hawley wrote: >On Tue, 29 Jul 2003, Post, Mark K wrote: > > > >>.. >>So, perhaps you need to modify your work practices rather than diddle with >>the software. Copy the locally updated files to another location so they're >>not clobbered when the remote version changes. >> >> > >indeed. consider creating local "copies" by instead just tracking >versions of your image files with RCS if its available for your system >(and if you aren't already using it): > >http://www.gnu.org/software/rcs/ > > To answer questons asked so far: We are using wget version 1.8.2 I have checked the dates on the local file and the remote file and the local file date is newer. The reason I thought it was still clobbering despite the newer date on the local was because of the size difference. I read that in the online manual here: http://www.gnu.org/manual/wget/html_chapter/wget_5.html#SEC22 At the bottom it says, "If the local file does not exist, or the sizes of the files do not match, Wget will download the remote file no matter what the time-stamps say." I do want newer files on the remote to replace older files on the local server. Essentially, I want the newest file to remain on the local. The problem I am having, however is that if we change/update files on the local, if they are of a different size, the remote copy is downloaded and clobbers the local no matter what the dates are. I hope this is clear, sorry if I have not explained the problem well. Let me know if you have anymore ideas and if you need me to try again to explain. Thanks for your help. Preston [EMAIL PROTECTED]
