Every year at day light savings time, the .ls_ file somehow gets the wrong datestamp in there and causes the poll script to download all the old files again.
can you provide an example server name?
I think the only way around this is to configure a 'timezone' for the remote host, and then convert to UTC on reading... I would have thought all the remote hosts were in UTC, so I don't get why this happens.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The server causing problems is sftp.gov.ab.ca. From the sftp prompt, I can't tell what time zone the remote server. But this issue keeps recurring every daylight savings change.
The FTP protocol, misdesigned as it is, doesn't include time zone information. This means client programs have to guess what the time zone of the server is.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
can you provide an example server name?
I think the only way around this is to configure a 'timezone' for the remote host, and then convert to UTC on reading... I would have thought all the remote hosts were in UTC, so I don't get why this happens.
The server causing problems is
sftp.gov.ab.ca. From the sftp prompt, I can't tell what time zone the remote server. But this issue keeps recurring every daylight savings change.Looking further into SFTP, I found this: https://ohse.de/uwe/ftpcopy/faq.html#timestamp
now: https://github.com/MetPX/sarracenia/issues/45