similar to: Date time problems

Running under Windows XP 64 bit, as.POSIXlt()/as.POSIXct() seem to think that US time zones (EST5EDT, MST7MDT) switched from daylight savings back to standard time on Oct 28, 2007, whereas the switch is actually on Sun Nov 04, 2007. Examples: > Sys.timezone() [1] "Mountain Daylight Time" > as.POSIXct("2007-10-30 12:38:47") [1] "2007-10-30 12:38:47 Mountain

Full_Name: Erich Neuwirth Version: 2.3.1 OS: Windows XP, Linux Submission from: (NULL) (131.130.135.167) Converting Sys.Date() to a POSIX compliant time type in different ways produces inconsistent results: > Sys.date() [1] "2006-09-01" > as.POSIXct(Sys.Date()) [1] "2006-09-01 02:00:00 CEST" > as.POSIXlt(Sys.Date()) [1] "2006-09-01" >

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 am thinking about using the G729 codecs on my endpoint devices and purchasing some G729 licenses for Asterisk but I have several questions: 1. Which G729 codec is sold by Digium for Asterisk, G729, G729A, B...I? 2. If I have G729A on one end and G729B on the other, are they compatible? I have looked all over the place for question 2, but without buying the ITU docs I cannot seem to find 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 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 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

The problem with POSIXt is that you must consider timezones and daylight vs. standard time issues even if you don't want to. This violates modularity (viz. your routines becomes coupled to unrelated information) and leads to subtle errors where different routines are assuming different time zones. The problem is that the time, date, day of the week, month, etc. of a date depend on its

Brian Wright wrote: > David, > > I was reading on Deja that you were having difficulties with Linux and > Windows with the daylight savings. I'm not sure how you're experiencing it. > My problem is when I mount Windows shares on Linux. The wierd thing is > this. Windows has the correct time set. Linux has the correct time set. > However, whenever I create a file

are your workstations w98 ?? or nt/w2k ?? (have the same here, only with w98 ws) you can also use net time /SETSNTP:ntp server Collen Friday, February 13, 2004, 3:45:21 PM, you wrote: TFGF> I already configured my time zone, daylight, etc..... TFGF> The server date is correct. I already compiled a TimeZone file(.ZIC) with TFGF> the correct date for DayLight saving. TFGF> The

Colleagues, I submitted this several days ago and no one responded, so I am trying again, trying a different subject line: 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 results below suggests that R (version 2.8.0 in OS X) implements the

Hi, I am in Australian. Now it is daylight saving time in Australian. I have daysaving time issue on samba client as below. On AIX server, I get the following two files's modified time via command istat. /zytest/file1 (Modified time: Fri Sep 18 12:07:37 EST 2009) /zytest/file1 (Modified time: Sun Nov 1 13:42:16 EDT 2009) On samba client Windows machine, the modified time

One problem with the daylight savings is that they mess with reporting tools that use timestamps. I guess an application could be configured to log UTC instead of local time, but that's not always doable. Also, if you have servers in several different timezones, it's better if all systems follow the same clock. So, I'm thinking it's perhaps better if I just use

When the Central European Time was last switched back to standard, at 03:00 last Sunday, the October 30th, a process died on one of my Windows clients with a mysterious "unknown error". When it was restarted it just went merrily on with its task. Luckily it wasn't part of a life support system. I found out that the immediate cause was how file timestamps were interpreted/presented

Hi, I have a whole bunch of data, which looks like: 15/03/2003 10:20 1 15/03/2003 10:21 0 15/03/2003 12:02 0 16/03/2003 06:10 0 16/03/2003 06:20 0.5 16/03/2003 06:30 0 16/03/2003 06:40 0 16/03/2003 06:50 0 18/03/2003 20:10 0.5 etc. (times given on a 24 hour clock) and goes on for years. I have some code:

Hi. I'm running on a Windows 98 client and an RS6000 with Samba 2.0.7 (latest). I've used "net time \\ibrissde /SET /YES" to sync the times between the two systems ... but if I save a file onto the RS6000 through Samba on a mapped drive the file in UNIX is 1 hour old. I haven't been able to find any help on this so I'm assuming it's a bug !? This was also true

Hello there, I have a samba PDC 3.0.0 running ok, but I had turned on the option "Time Server" in smb.conf, to synchronize the workstations time with server. But the workstations synchronize 1 hour less than it is. I think that the workstations isn?t considering the daylight saving time. I?m using the command: net time \\server /set /yes Thank?s, []?s Tercio

Hello, I must be doing something wrong that's very obvious. But I just don't see it. I changed my Windows Time Zone to GMT and my Financial Center to Montreal. But I still get several warnings. >Sys.timezone() [1] "GMT Daylight Time" >myFinCenter [1] "Montreal" >Sys.timeDate() [1] "Montreal" [1] [2005-04-19 10:55:02] Warning messages: 1: Set

I have some questions and comments on timezones. Problem 1. # get current time in current time zone > (now <- Sys.time()) [1] "2003-07-29 18:23:58 Eastern Daylight Time" # convert this to GMT > (now.gmt <- as.POSIXlt(now,tz="GMT")) [1] "2003-07-29 22:23:58 GMT" # take difference > now-now.gmt Time difference of -5 hours Note that the difference

I think the following examples illustrate the crux of the matter (version and OS info are below). The problem has to do with the transition from standard time to daylight savings time. My timezone, US/Pacific, has two parts: standard time (PST) 8 hours behind GMT and daylight savings time (PDT) 7 hours behind GMT. The transition takes place this year on 7 April at 02:00, when 02:00 is