similar to: So-called 'bug' reports PR#8102 and PR#8103

Hi All In trying to correlate some tide gauge data I need to deal with varying timezones. From the documentation on strptime, it seemed that the tz variable might have some effect on the conversion, but I'm not seeing an effect. > strptime("20061201 1:02 PST",format="%Y%m%d %H:%M",tz="PST")+0 [1] "2006-12-01 01:02:00 EST" >

On the documentation page for DateTimeClasses, in the Examples section, there are the following two lines: format(.leap.seconds) # the leap seconds in your time zone print(.leap.seconds, tz = "PST8PDT") # and in Seattle's The second line (using print) seems to ignore the tz argument, and prints the dates in my time zone, while: format(.leap.seconds, tz =

on hp-ux 11 i see: $ date;ssh jenny Fri Oct 12 14:44:13 PDT 2001 Last successful login for stevesk: Fri Oct 12 10:45:42 PST8PDT 2001 on pts/2 Last unsuccessful login for stevesk: Mon Sep 24 22:55:53 PST8PDT 2001 Last login: Fri Oct 12 10:45:43 2001 from 172.31.1.53 You have mail. so solaris PAM is different. can other solaris+PAM users confirm this? On Fri, 12 Oct 2001, Benn Oshrin wrote:

Hi, I''ve been trying to do timezone conversion, and have some trouble getting it to work on my Windows machine. Searching the web, I found http://wiki.rubyonrails.com/rails/pages/HowtoSetDefaultTimeZone ...which explains how to set the default timezone. I''m using an environment.rb that include the lines: ActiveRecord::Base.default_timezone = :utc ENV[''TZ''] =

I am analysing some data collected over a number of months from Allentown, PA, which is just north of Philadelphia. I am using as.POSIXct for dates and times, and I need to get the timezone specification correct. Going on the documentation for DateTimeClasses, I believe one way to specify the correct time zone is tz="EST5EDT" I would be grateful for any advice on this. I ask

Hi, I have two data sources. One records time in PST time zone, the other in GMT. I want to compute the difference between the two, but don't see how. Here is an example where I compute time difference between identical times each (meant to be) relative to its time zone. > as.POSIXlt("2000-05-10 10:15:00", "PST") - as.POSIXlt("2000-05-10 10:15:00",

Hello, I'm having a major problem with the timestamps in both the Icecast access.log and error.log. The timestamp on the logfiles themselves is accurate, but the logging of the various connections to my streams is in UTC. No matter how I try to configure the hwclock or the system clock, the log timestamp is always UTC, which is 8 hours ahead of my current time zone. I've even tried

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

There is incompatibility between R strptime and musl libc. I posted about it on their mailing list, but they need more information I can't provide, so I'm forwarding the message here in hope R developers can help. Thanks. ---------- Forwarded message ---------- From: Rich Felker <dalias at libc.org> Date: Thu, Feb 4, 2016 at 2:07 PM Subject: Re: [musl] strptime() question To: Alba

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

Greetings - I'm battling POSIXct, as per the code below. My input is actually an XL file, but the weird results below correctly model what I am seeing in my program. Before I punt and use lubridate or timeDate, could anyone please help me understand why POSIXct forces my variable back to GMT? I suspect that I'm not properly coding the tzone value, but it does not throw an

Hello! I've time stamp ('time') field in dataset ('dt') with values like "18:10", "19:43", .... I need to split time field into hour and minutes and add both as new columns to dataset. We are able to do it in bash+awk, but curious to stay within R codebase as much as possible. For now we are using such solution: tstamp <- strsplit(dt$time,

Sorry for the extra info required, but I had digest mode turned on and wouldn't have received the mailing till tomorrow. I have since updated the data manually, but after 'yum update tzdata' was run, the zdump -v for EST5EDT and America/New_York all still showed a date of April 1, instead of March 11. After manually fixing, it is correct. This was mostly a question about why yum

I have timstamped data like this: > sd[1:10,] Tstamp Density Mesh50 Mesh70 Mesh100 Mesh150 Mesh200 2 2009/02/27 07:00 30.5 0.7 10.7 21.4 32.8 41.6 3 2009/02/27 08:00 32.2 1.6 12.4 23.3 34.5 43.0 4 2009/02/27 09:00 32.7 4.8 13.0 24.0 35.1 43.5 5 2009/02/27 10:00 26.7 0.3 6.5 17.6 28.1 36.9 6 2009/02/27 11:00

https://bugzilla.netfilter.org/show_bug.cgi?id=1066 Bug ID: 1066 Summary: nfq_get_timestamp() not setting timeval struc Product: libnetfilter_queue Version: unspecified Hardware: x86_64 OS: Ubuntu Status: NEW Severity: normal Priority: P5 Component: libnetfilter_queue

Can anyone tell me what I missed? I'm trying to setup a simple extension (400) that reports the time when it is dialed. I searched the threads and it seems like this should work... Here's what's in my extensions.conf: exten => 400,1,Answer() exten => 400,n,Wait,1 exten => 400,n,SayUnixTime(,EST5EDT,) exten => 400,n,Playback(tt-weasels) [BTW, tt-weasels is hillarious!

This replaces the build dependency on perl with one on awk which is already used in the build system and is much more ubiquitous than perl --- Makefile.in | 2 +- mkproto.awk | 39 +++++++++++++++++++++++++++++++++++++++ mkproto.pl | 48 ------------------------------------------------ 3 files changed, 40 insertions(+), 49 deletions(-) create mode 100644 mkproto.awk delete mode 100644

>>>>> Jennifer Lyon <jennifer.s.lyon at gmail.com> >>>>> on Thu, 15 Dec 2016 09:33:30 -0700 writes: > On the documentation page for DateTimeClasses, in the Examples section, > there are the following two lines: > > format(.leap.seconds) # the leap seconds in your time zone > print(.leap.seconds, tz = "PST8PDT") # and in

I have a fairly large set of data with the following attributes: >str(raw.data) `data.frame': 1429 obs. of 16 variables: $ TStamp :`POSIXlt', format: chr "2001-11-25 02:00:00" "2001-11-25 01:55:00" "2001-11-25 01:50:00" "2001-11-25 01:45:00" ... $ iPDT.AHU14.14: num 0.0122 0.0125 0.0120 0.0120 0.0122 ... $ iPDT.AHU14.15: num 0.0121

hey list! having a slightly odd time issue on one host... can I get some help with this? This is the current time from a working system: Sun Apr 17 00:28:18 EDT 2011 However from the problem system this is the time: Sat Apr 16 20:30:01 EDT 2011 I have set the time zone as such: lrwxrwxrwx 1 root root 23 Apr 16 19:41 /etc/localtime -> /usr/share/zoneinfo/EST But when I run ntpdate