similar to: 3.8p1 not honoring TZ environment variable

Displaying 20 results from an estimated 2000 matches similar to: "3.8p1 not honoring TZ environment variable"

2007 Nov 01
1
daylight saving / time zone issues with as.POSIXlt/as.POSIXct (PR#10392)
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
2007 Oct 30
1
timezone conversion difficulties with the new US daylight saving time switch over
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") #
2007 Nov 01
0
daylight saving / time zone issues with as.POSIXlt/as.POSIXct (PR#10393)
tplate at acm.org wrote: > 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. > > =20 Not Our Problem. (This sort of thing never is. We are wholly dependent=20 on the OS for this information).
2006 Jun 07
4
Setting default timezone ENV[''TZ'']=''UTC'' not working on windows?
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''] =
2007 Jan 08
1
Does strptime(...,tz="GMT") do anything?
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" >
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
2016 Feb 04
3
Fwd: [musl] strptime() question
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
2005 Sep 22
1
SayUnixTime in CVS?
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!
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
2005 Aug 31
1
So-called 'bug' reports PR#8102 and PR#8103
Neither of these have reached me on R-devel (and only PR#8103 is on the archive), and they seem to be the same error although neither mentions the other. That's 'odd', to quote one of them. "EDT" is not a valid POSIX timezone (but, say, EST5EDT is). R's docs are quite clear that what happens with invalid inputs is system-specific. (Windows seems often to run home
2004 Apr 06
2
[Bug 834] timezone settings on irix lost
http://bugzilla.mindrot.org/show_bug.cgi?id=834 Summary: timezone settings on irix lost Product: Portable OpenSSH Version: 3.8p1 Platform: All OS/Version: IRIX Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy: ktaylor at
2004 Aug 09
1
Time zones
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
2003 Dec 05
6
ssh not resolving host names on HP-UX 11i
Actually it really never was answered, but here's how I fixed (worked around) it. At first I thought installing patch PHNE_27796 (libnss_dns DNS backend patch) had fixed it. It didn't. It just flip-flopped the problem. Prior to installing that patch, ssh would never go to DNS no matter what was in nsswitch.conf. It appeared to only look in /etc/hosts. After installing the patch, ssh
2004 Apr 08
1
openssh-3.8p1 fails to set TZ environment variable bug
Found on while running on IRIX 6.5.22f, sshd from openssh-3.8p1 nukes its envrionment in main(), causing sshd to loose track of the TZ environment variable passed to it by the system. This means that inside do_setup_env(), the call to getenv("TZ") will never succeed, despite the fact that this variable should have a value.
2011 Apr 17
3
timezone issue
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
2020 Oct 23
0
timezone tests and R-devel
So let me try to raise this issue once more, and perhaps be more clear about what I think the issue is.. In my opinion there is now a bug in make check in R-development (tested today with r79361). As I see it, I specify a reasonable TZ environment variable and this leads to make check emitting an error. Best, Kasper On Fri, Oct 2, 2020 at 11:28 AM Kasper Daniel Hansen < kasperdanielhansen
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
1
timezone tests and R-devel
Yes, you are absolutely right and I'm pretty sure this will be fixed in one way or another. IMO, the failing test should simply use all.equal.POSIXt's new argument check.tzone=FALSE. Two simple alternatives modifying all.equal.POSIXt behaviour: - make check.tzone=FALSE the default: this is inconsistent with other arguments of all.equal methods, always defaulting to stricter checks -
2006 Sep 12
3
Weird TZ Behavior in 4.1p1 and 4.3p2 on AIX
Hi, I am using PAM authentication on 3.8p1. In my PAM auth module I can turn on debug logging that includes a timestamp in the form "mm/dd/yy hh:mm:ss". Life is good. I want to upgrade from 3.8p1 so I can use PAM for PasswordAuthentication in addition to keyboard-interactive. I have compiled both 4.1p1 and 4.3p2 and the PAM authentication for both methods works fine in both
2007 Oct 27
1
Unwanted axis labels when rug() has POSIXlt argument (PR#10380)
rug() may add integer axis labels when called with a POSIXlt object as argument. dtimes <- c("09/29/2007 12:54", "09/30/2007 00:14", "10/01/2007 00:14", "10/02/2007 00:14", "10/03/2007 00:14", "10/04/2007 00:14", "10/05/2007 00:14", "10/06/2007 00:14", "10/07/2007