similar to: Undocumented behavior around daylight savings time?

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

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

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

Quoting cosmin at speakeasy.net, on Sat, May 20, 2006 at 11:40:06AM -0700: > I did some changes to the rrule.rb. I needed some getters/setters for > each of the attributes from RRULE. Attached is the diff. If it makes > sense to you to be included in the lib, please do so. If you think > it''s worth to be included, I can add more validation to the setters. I

I'm having problems entering dates and times around when daylight savings time starts. If I type (on R 1.8.1 on Gentoo Linux) > ISOdatetime(2004,4,4,0:4,0,0,"GMT") [1] "2004-04-03 19:00:00 EST" "2004-04-03 20:00:00 EST" [3] "2004-04-03 22:00:00 EST" "2004-04-03 22:00:00 EST" [5] "2004-04-03 23:00:00 EST" Giving the times

Who is tired of dealing with DST changes? I have asterisk running on FC4, FC4 has been patched and shows the correct MDT timezone and time. Email notifications of voicemail show the message time an hour early (standard time, not daylight). This si the time in the message body, not the email delivery time, so it is coming form asterisk wrong. I did a reload after correcting the

Hi all, Running Samba 4.0.0apha18 with good results but getting an error when I attempt to replicate the Global Catalog to a Windows 2008 Machine. Samba machine = DC1 Windows 2008 machine = DC0 samba-tool Showrepl result: Default-First-Site-Name\DC1 DSA Options: 0x00000001 DSA object GUID: 05c3c860-0a0d-4672-a39e-a212ccb0ce9c DSA invocationId: abb0cab3-13d3-456c-8a16-e65a4855a2df ==== INBOUND

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

Hi, we had the same problems last year and we use NTFS. Luckely we switched to Linux this year. Kind regards, Bart Coninckx Network Administrator CNE, ASE ************************************* Sita ICT Services Lilsedijk 19 B-2340 Beerse Belgium e-mail: bart.coninckx@sita.be Tel: + 32 (0) 14 62 28 22 Fax: + 32 (0) 14 62 41 47 *************************************

I have a simple worker that I set up with repeat_every: class DueNoteQueuerWorker < BackgrounDRb::Rails repeat_every 1.minutes first_run Time.now def do_work(args) @logger.debug("Sending due notes. The current time is #{Time.now}") end end I want this to run every minute, all the time. The first run is fine, but it seems that subsequent runs get executed

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

I''m evaluating lustre. I''m trying what I think is a basic/simple ethernet config. with MDT and OST on the same node. Can someone tell me if the following (~150 second recovery occurring when small 190 GB OST is re-mounted) is expected behavior or if I''m missing something? I thought I would send this and continue with the eval while awaiting a response. I''m using

Hi, How do I convert a numeric value indicating the time since 1970, back into a POSIXct class object? I have tried format.POSIXct and as.POSIXct without success. For example > ccc [1] "1945-01-01 15:00:00 MDT" > ddd<- as.numeric(ccc); > ddd [1] -788842800 > format.POSIXct(ddd) Error in format.POSIXct(ddd) : wrong class > as.POSIXct(ddd) Error in

In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to use pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE script. The relevant portion of my PXELinux config looks like this: LABEL MDT MENU LABEL ^B - MDT 2012 SP1 com32 pxechn.c32 APPEND undionly.kpxe -o 67.s=ipxe/mdt.ipxe However iPXE doesn't seem to get the option correctly, it goes into

Article by Jeff Layton: http://www.linux-mag.com/id/7839 anyone have views on whether this sort of caching would be useful for the MDT? My feeling is that MDT reads are probably pretty random but writes might benefit...? GREG -- Greg Matthews 01235 778658 Senior Computer Systems Administrator Diamond Light Source, Oxfordshire, UK

This may be in the documentation. If so, I missed it. If a site has multiple Lustre file systems, the documentation implies that there only needs to be a single MGS for an entire site (regardless of the number of file systems). However, I also know it is fairly common to have a combined MGS/MDT. So here are the questions. 1. If we are going to have several Lustre file systems,

On Tue, Jul 16, 2013 at 6:26 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette > <blanalex at gmail.com> wrote: > > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to > use > > pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE > > script. > > > > The

Dear all, Two of our MDS have got repeatedly read-only error recently after once e2fsck on lustre 1.8.5. After the MDT mounted for a while, the kernel will reports errors like: Oct 8 20:16:44 mainmds kernel: LDISKFS-fs error (device cciss!c0d1): ldiskfs_ext_check_inode: bad header/extent in inode #50736178: invalid magic - magic 0, entries 0, max 0(0), depth 0(0) Oct 8 20:16:44 mainmds

Buenas tardes, Estoy probando a leer archivos netcdf (como raster stack) y crear animaciones de datos de modelos climáticos y estaba utilizando para generar las imágenes spplot(). Estás imágenes tienes superpuestas varias capas de imagenes, el mdt de base, nubosidad, precipitación y nieve. Mi pregunta es la siguiente,¿es posible visualizar la leyenda de cada una de las capas? Actualmente solo