similar to: tzdata - extra info.

I read a few days back on the list where the tzdata rpm was to take care of the new DST rules. I run CentOS 3 servers, and did a 'yum update tzdata' , but received a 2006a update of the rpm. Is this proper? It sure didn't fix anything. Thanks Steve Campbell campbell at cnpapers.com Charleston Newspapers

> 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

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

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

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:

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:

I tested moving a box from Tao 1.0 to CentOS 3.7. All went well, as far as I can tell, with the OS upgrades, but I needed to rpm -ivh --force the desktop-* stuff. This was a minor thing to fix for no real purpose other than to just be doing it. I still get, though, the Tao screens when the graphic login screen appears. I have changed the Application->Settings->Login Screen->

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 <-

I'm running CentOS 3 and have just installed a Liteon lightscribe DVD/CD unit. I firstly realized I didn't know exactly how to mount it, as /dev/dvd didn't exist, I didn't want to generate anything if it already existed, and I didn't want to mess up my cdrom unit that works just fine. I mounted the device though the X window just to see how it might mount, and find that it

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

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" # =

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" # =

Mr. Parsley, the main man at the Tao Linux group, has announced that he will no longer be able to do his thing for Tao Linux. Just recently, I had decided to investigate CentOS 4 before his announcement, and liked a lot of what I saw. Due to the Tao announcement, I have decided that CentOS will "have" to be the OS for my company in the future. Hence, my new membership to this list.

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?

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:

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" >

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

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

> 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

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