I still can't understand how winscp has any part in this. I don't copy anything, I only use it to view the files. Tomcat automatically creates the .java and .class files. I could use putty or some other tool and the result would be the same. But it's even wierder. Now I see even the catalina.out file (which is updated very often) has the timestamp +1 hour. Like that wouldn't be enough, the servers are in Italy, where the time is now 9:05 (so the server time is 9:05), i'm in Romania where the time is 10:05, and catalina out was last modified(aparently) at 11:05. .... too wierd
----- Original Message ---- From: David Smith <[EMAIL PROTECTED]> To: Tomcat Users List <users@tomcat.apache.org> Sent: Tuesday, April 8, 2008 10:49:35 PM Subject: Re: tomcat cache wierd behaviour Winscp isn't a command line tool -- it's one of those GUI enabled transfer tools with the split panels. Think of something more along the lines of Explorer or Norton Commander -- the two interfaces styles available from winscp out of the box. By default it set's the date/time of the recently sent file to the client's date/time so it can implement a synchronize feature. I changed the settings in mine to prevent this because my server time would float a little between ntp updates. Tomcat wouldn't see the updates until a couple of minutes after I uploaded them. Issues of times on the remote system being off by an hour are discussed on the winscp website (as the OP described in his example in the original post): http://winscp.net/eng/docs/timestamp The setting to preserve timestamps on uploads can be changed: http://winscp.net/eng/docs/ui_copy -- here you can see the checkbox labeled "Preserve timestamp" in the screenshot, far right side under 'Attributes'. --David Christopher Schultz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > David, > > David Smith wrote: > | I've seen some transfer clients (like winscp) default to setting the > | date/time on the remote copy the same as the local. > > If 'winscp' acts anything like UNIX scp, then the default mode is to set > the modification time on the destination to the destination's current > date (basically, 'touch' the file upon creation). The "-p" switch allows > you to preserve the existing modification time of the source file, so > that the destination matches the source after the copy. It's unclear how > different time zones are handled. > > I would check to see what 'winscp' does by default. You probably want > any files you copy to your server to be date-stamped with the current > date on the server, rather than preserving the source file's > modification time. > > The OP never mentioned what the timezone was on the source machine, only > the destination (CEST, UTC +2). > > - -chris > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkf7xUUACgkQ9CaO5/Lv0PCT8gCggO1z8trzf40N1YNbgAgy0cUP > SjkAoJqJiFYvg56JthbKEkFihH3LARPq > =LrfO > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
