similar to: tzdata

Displaying 20 results from an estimated 1000 matches similar to: "tzdata"

2007 Feb 07
4
tzdata - extra info.
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
2015 Jun 23
4
yum and yumex change system time
> Date: Tuesday, June 23, 2015 03:48:36 PM -0400 > From: Jonathan Billings <billings at negate.org> > > On Tue, Jun 23, 2015 at 01:56:13PM -0500, g wrote: >> each and every time i run yum or yumex, system time is advanced >> by 5 hours. >> >> this has gone on thru several updates, maybe even upgrades. >> >> centos = 6.6 current >> yum
2008 Jun 11
2
time on asterisk
Hi, I'm using gotoiftime on asterisk, but it seems&nbsp; there is a difference between the asterisk time and the system time. could it be because i adjusted the system timezone on my linux? do asterisk not detect the change of timezone on the system? How can I fix this prob? Regards, nhadie -------------- next part -------------- An HTML attachment was scrubbed... URL:
2015 Jun 23
2
yum and yumex change system time
Richard, thank you for your response. On 06/23/2015 02:51 PM, Richard wrote: <<>> > I agree, so my questions are: > > - what is your TZ? u.s.a. 'central time zone' - currently on 'daylight savings time'. > - what does "[/bin/]date" show? [geo at boxen ~]$ date Tue Jun 23 14:54:42 CDT 2015 > - what does your hardware clock:
2020 Oct 01
3
timezone tests and R-devel
The return value of Sys.time() today with a timezone of US/Eastern is unchanged between 4.0.3-patched and devel, but on devel the following test fails all.equal(x, as.POSIXlt(x)) with x = Sys.time() This means that devel does not complete make tests (failure on tests/reg-tests-2.R) It is entirely possible that it is an error on my end, I use export TZ="US/Eastern" but I have been
2020 Oct 23
2
The presence/absence of `zone` in POSIXlt depending on time zone as a cause of possible inconsistences?
Dear all, I have just detected what seems a minor inconsistence with data types. If one unlists a POSIXlt time with GMT zone gets a numeric vector, since the POSIXlt list has no `zone` element, while if one unlists a POSIXlt time with a non GMT zone (also non specifying tz if the Sys.timezone is not GMT) gets a character vector due to including the `zone` element. > x <-
2012 Dec 06
1
Incorrect DST time changes in DateTimeClasses
Can anyone please shed any light on why R DateTimeClasses give weird times for when daylight saving time information changes, and which aren't consistent with the OS? Example: Expected result: in New Zealand DST stopped (NZDT -> NZST) at 03:00 NZDT on 2010-04-04, as confirmed by the OS time zone info (OS X 10.8.2): zdump -v /etc/localtime /etc/localtime Sat Apr 3 13:59:59 2010 UTC
2017 May 17
2
R-3.4.0 fails test
After installing R-3.4.0 I ran 'make check' which halted here: $ > tail reg-tests-1d.Rout.fail -n 16 > ## format()ing invalid hand-constructed POSIXlt objects > d <- as.POSIXlt("2016-12-06"); d$zone <- 1 > tools::assertError(format(d)) > d$zone <- NULL > stopifnot(identical(format(d),"2016-12-06")) > d$zone <- "CET" # =
2017 May 17
2
R-3.4.0 fails test
After installing R-3.4.0 I ran 'make check' which halted here: $ > tail reg-tests-1d.Rout.fail -n 16 > ## format()ing invalid hand-constructed POSIXlt objects > d <- as.POSIXlt("2016-12-06"); d$zone <- 1 > tools::assertError(format(d)) > d$zone <- NULL > stopifnot(identical(format(d),"2016-12-06")) > d$zone <- "CET" # =
2020 Oct 02
2
timezone tests and R-devel
Yes, the potential issue I see is that make check fails when I explicitly set TZ. However, I set it to be the same as what the system reports when I login. Details: The system (RHEL) I am working on has $ strings /etc/localtime | tail -n 1 EST5EDT,M3.2.0,M11.1.0 $ date +%Z EDT $ echo $TZ US/Eastern On Fri, Oct 2, 2020 at 9:48 AM Sebastian Meyer <seb.meyer at fau.de> wrote: > Thank
2015 Jun 24
0
yum and yumex change system time
On 06/23/2015 04:47 PM, g wrote: > > Richard, thank you for your response. > > > On 06/23/2015 02:51 PM, Richard wrote: > <<>> > >> I agree, so my questions are: >> >> - what is your TZ? > > u.s.a. 'central time zone' - currently on 'daylight savings time'. > >> - what does "[/bin/]date" show?
2017 May 18
2
[R] R-3.4.0 fails test
On Wed, 17-May-2017 at 01:21PM +0200, Peter Dalgaard wrote: |> |> Anyways, you might want to |> |> a) move the discussion to R-devel |> b) include your platform (hardware, OS) and time zone info System: Host: MTA-V1-427894 Kernel: 3.19.0-32-generic x86_64 (64 bit gcc: 4.8.2) Desktop: KDE Plasma 4.14.2 (Qt 4.8.6) Distro: Linux Mint 17.3 Rosa Machine: System:
2014 Jun 03
3
error de incompatible methods
Hola!! Estoy intentando ejecutar un script com horas, al principio ejecute estos comandos DBx$Date<-strptime(DBx$Date, "%d-%m-%Y") ###Monicap use ; other use Y DBx$Year<-as.POSIXlt(DBx$Date)$year+1900 if(filename!="monicap_50.csv") {DBx$Time<-paste(DBx$Time, ":00", sep="")} Pero me daba el error de que mi base de datos tenia las
2017 May 18
2
[R] R-3.4.0 fails test
This has to do with your own timezone. If I run that code on my computer, both formats are correct. If I do this after Sys.setenv(TZ = "UTC") Then: > cbind(format(dlt), format(dct)) [,1] [,2] [1,] "2016-12-06 21:45:41" "2016-12-06 20:45:41" [2,] "2016-12-06 21:45:42" "2016-12-06 20:45:42" The reason for that, is that
2017 May 18
2
[R] R-3.4.0 fails test
> On 18 May 2017, at 13:47 , Joris Meys <jorismeys at gmail.com> wrote: > > Correction: Also dlt uses the default timezone, but POSIXlt is not recalculated whereas POSIXct is. Reason for that is the different way values are stored (hours, minutes, seconds as opposed to minutes from origin, as explained in my previous mail) > I would suspect that there is something more subtle
2014 Jun 04
2
error de incompatible methods
Hola Daniel, si perdona di a responder directamente y no me di cuenta. Ya se donde esta el error, pero queria preguntar si a puede ser que mi R funcione mal o algo porque esta manhana ejecute mi script y funciono perfectamente y ahora volvi a ejecutarlo y me volvio a dar el mismo problema de ayer , despues de reiniciar y demas el tinnR y el R, no se si me vacila o es que tengo algo mal en
2007 Mar 06
3
Time Change: Centos-immune?
hey all, I perused my inbox looking for this subject, but not finding it, -anything I need to keep my server farm of 60 centos servers (that all run ntp) going smoothly during this next time change on March 11? I noticed on the w2k side my IT staff have to do some scrambling, heh, but that's expected. Any action required? -karlski
2003 Mar 06
1
Timezones
Can anybody give me a hint why as.POSIXlt doesn't recognize the same timezones that zdump knows about (Linux Suse 8.1 and Suse 7.3)? Is there a workaround? R : Copyright 2002, The R Development Core Team Version 1.6.1 (2002-11-01) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type `license()' or `licence()' for
2015 Jun 23
3
yum and yumex change system time
greetings, each and every time i run yum or yumex, system time is advanced by 5 hours. this has gone on thru several updates, maybe even upgrades. centos = 6.6 current yum = 3.2.29 yumex = 3.0.5 for awhile, i did not mind resetting clock when i noticed it off. now, it is a pita because when i forget, emails and what ever else i am doing get wrong time stamps. i have searched for
2004 Oct 28
2
POSIX time anomaly (PR#7317)
Full_Name: Allen McIntosh Version: 2.0.0 OS: RedHat 9.0 Submission from: (NULL) (67.80.175.118) The POSIX time printing routine gives strange results when asked to print a time that is exactly midnight: TZ=CST6CDT R -q --no-save > strptime("10/5/2004 00:00:01 CDT", "%m/%d/%Y %H:%M:%S %Z") [1] "2004-10-05 00:00:01" > strptime("10/5/2004 00:00:00