scripting with timezone offset
Is it possible to pass a timezone offset using winscp in batch moe w/o calling a session? Or to use the preserver or "set" the timezone of the remote file to match the originating server after the fact?
My problem is that i synchronize 100s of thousands of files between 2 servers daily. Since 85% of the files don't change, it only grabs the new files. The problem is that any files that are "updated" at 11pm on any day are reported by winscp locally on the destination server as the next day, so they appear to be an entire day off. These files will always synchronize and copy during a "criteria=both" or "criteria=date". I'm trying to find a way to get them not to synchronize just for 1 hour offset. So i was thinking i could use timezone offset -1 to try and get the locals to seem like the same as the originating server. However i cannot seem to find an "option" or cmdline way to set the timezone offset to "-1". Is this even available?
Both servers have DST turned on and both are set to update to time.windows.com and are both exactly the same OS and have the same time.
Ideas?
My problem is that i synchronize 100s of thousands of files between 2 servers daily. Since 85% of the files don't change, it only grabs the new files. The problem is that any files that are "updated" at 11pm on any day are reported by winscp locally on the destination server as the next day, so they appear to be an entire day off. These files will always synchronize and copy during a "criteria=both" or "criteria=date". I'm trying to find a way to get them not to synchronize just for 1 hour offset. So i was thinking i could use timezone offset -1 to try and get the locals to seem like the same as the originating server. However i cannot seem to find an "option" or cmdline way to set the timezone offset to "-1". Is this even available?
Both servers have DST turned on and both are set to update to time.windows.com and are both exactly the same OS and have the same time.
Ideas?
