similar to: Solution For Rsync and Cygwin Daylight Savings Timezone Problems

That's actually a very good suggestion. First I figured that in this way files changed within the hour after creation would be ignored, but they probably represent a very small minority anyway. On the other hand, this does not really rectify the situation, but will allow us to postpone the real sync again until, let's say a holiday, where we have plenty of time to sync. Rgds, Bart

Hi, just a small warning about something that has, like we experienced just last weekend, great consequences. We rsync more than 20 Netware servers through a mapping on an NT machine to central Rsync destination servers (also NT). Last weekend our clock changed to Daylight Savings Time. It appears that NT changes the file stamps on NTFS volumes accordingly (Q129574 on their suppor site). This

Does anyone know the best way to track time zone information. There doesn''t seem to be much documentation on this. So far it seems like a simple db field like create table accounts ( id int unsigned not null auto_increment, name varchar(50) not null, time_zone varchar(50) not null, ... primary key (id) ) and a class like class Account < AR ...

Hi Folks, how do you handle the change from standard time to daylight saving time? We are using LotusNotes 6.5.1 and Wine 20041019 on Kubuntu 5.10 Breezy Badger. This is the combination where we experienced the least amount of Bugs. Our hosts run UTC on the hardwareclock and live in the timezone Europe/Vienna, which will change from CET to CEST on sunday. Tests have shown, that

Hi all, I've been having some trouble with times in regards to daylight savings in R version 2.8.1. I have an ORACLE database that R is importing data in from, for the 2am and 2:30am time intervals for the dates that daylight savings starts the times are getting read as NA values into R. I'm also finding that if I open a R workspace from version 6.2.2,the datetimes are

I'm having difficulties with daylight saving times in US time zones. (Apologies for the long post, but the problem seems subtle and complex, unless I'm doing something completely wrong, in which case it should be evident from the first 10 lines below.) This is what I see, using a (slightly modified) example from ?as.POSIXlt : > as.POSIXlt((d <- Sys.time()), "EST5EDT") #

I have found what looks like a small problem in trunc.POSIXt() involving the transition to/from standard time and daylight savings time. Assuming my assessment is correct, I have a potential solution to offer. If a time in daylight savings time is rounded such that the rounded value is on the other side of the transition, the isdst element does not get changed accordingly. I have tested only

This message, hopfully, summarizes all the questions people may have about the change affecting when Daylight Savings Time begins and ends for various time zones which takes effect this year. NOTE: Before you decide this message does not effect you please bear in mind that the most critical file involved in all of this is /etc/localtime. That is the zoneinfo file your system will be using to

I have a data frame that contains dates, but when I use as.POSIXlt() I lose the hours on all records. I traced this down to a particuar hour which causes the issue... > as.POSIXlt('2004-10-31 02:00:00') [1] "2004-10-31" > as.POSIXlt('2004-10-31 03:00:00') [1] "2004-10-31 03:00:00" How do I tell as.POSIXlt() to ignore daylight savings and just convert to

*Hi All, * I presume the upstream provider is aware of this??? I am in Indiana. Go figure. Jerry ** *---------------- * *New Federal Law?Springing Forward in March, Back in November* Months after Indiana passed the law that got it in step with the rest of the country, the federal government announced a major change in Daylight Saving Time. In Aug. 2005, Congress passed an energy bill that

> Date: Wed, 13 Aug 1997 12:52:21 -0700 > From: "Roeland M.J. Meyer" <rmeyer@mhsc.com> > To: eknuds@extremenetworks.com > Cc: "samba@arvidsjaur.anu.edu.au" <samba@arvidsjaur.anu.edu.au> > Subject: Re: Linux smbfs 2.0.29... > Message-ID: <3.0.2.32.19970813125221.009e0a70@pop.mhsc.com> > > At 04:45 AM 8/14/97 +0000, you wrote: > >I

The following code: cut(as.POSIXct("2009-11-01 04:00:00", tz="America/Los_Angeles"), "1 day") gives the error: Error in seq.int(0, to - from, by) : 'to' must be finite This is related to November 1st, 2009 being the switchover date from daylight savings time to standard time in the America/Los_Angeles time zone. In particular, in cut.POSIXt, the starting

I have asked this question before, and received some suggestions for work-arounds that get the job done--and they are much appreciated. But I would still like to find out if I'm missing something, and whether there is a direct way using POSIXt functions (as.POSIXct, as.POSIXlt, strptime, in particular). I have environmental data collected once per minute. Here is a subset of 3 input

Under R-2.2.1, a POSIXlt date created with "strptime" has an unknown Daylight Savings Time flag: > strptime(20051208, "%Y%m%d")$isdst [1] -1 This is true on both Linux (details below) and Windows. It did not occur under R-2.1.0. Any ideas? TIA! > Sys.getenv("TZ") TZ "" Version: platform = i686-pc-linux-gnu arch = i686 os = linux-gnu

I'm searching for an r command that will notify me if I create a time that does not exist due to Daylight Savings Time. For example, if I run the following command on a windows machine > ISOdatetime(2010,03,14,2,10,0, tz = "") # My system time is set to the United States Central Time Zone [1] NA R returns NA, which is the behavior I want. However, if I run the same command on a

Colleagues, I just encountered some unexpected behavior of difftime in relationship to the change from daylight savings to standard time. My understanding is that DST and ST take effect at 2AM. However, the code below suggests that R (version 2.8.0 in OS X) implements the change at 2:16AM: Expected: > > difftime("2008-11-02 02:01:00", "2008-11-02 00:59:00")

Hi all, I wanted to check this with you. I have an rspec example that checks the correct expiration date set on an object. The expiration is set in the model with expires_on = Time.now + next_duration[phase] where next_duration can either be in units of seconds or n.days (should be the same thing). n can be 3, 7, 25, or 30 days. in my example I check an interval because the two events are not

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=75 netfilter@linuxace.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |netfilter@linuxace.com Status|ASSIGNED |RESOLVED Resolution|

I'm running 2.2.6 When daylight savings time changed this weekend I had to reset all samba sessions as the sessions didn't pick up the time change. Copying file from a Windows client to the server made the filetime off by one hour. Killing all the same sessions (also restarted smbd -- not sure if that was needed) fixed the problem. Michael D. Black mblack@csi-inc.com

Hi all, I'm currently testing the Novell Netware version of Rsync 2.5.5. I use a RH 80 linux client, the Novell server runs the daemon. The Novell server has 850 (=latin1 ?) as codepage and users sometimes create filenames with "odd" (international) characters in them. These appear to be converted into other characters or question marks by rsync, or are simply left out. I've