similar to: Samba bug: 1 out of 387 files off by 1 hour (DST/ST bug)

FYI, the same bug apears if one mounts the file system using "cifs": -rwxr----- 1 user 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3* -rwxr----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3* Linda W wrote: > Summary: > There appears to be a bug in the "time range" Samba is using on > dates where time is scheduled to "Spring Forward"

I am having problem using output of lm() function for further analysing using systemfit package. Basicaly, the problem s following - I generate several formulas using lm() > fo1 <- lm(r98[,2] ~ f98[,1] + f98[,2] + ... + f98[,43]) > fo2 <- lm(r98[,1] ~ f98[,1] + f98[,2] + ... + f98[,43]) and than I want to estimate a general model using package systemfit. > fitsur <-

Dear list, I would like to do some calculation using different grouping variables. My 'df' looks like this: # Some data set.seed(345) id <- seq(200,400, by=10) ids <- sample(substr(id,1,1)) group1 <- rep(1:3, each=7) group2 <- rep(1:2, c(10,11)) group3 <- rep(1:4, c(5,5,5,6)) df <- data.frame(id, ids, group1, group2, group3) df <- rbind(df, df, df) df$time <-

It is clear, I think, that is.vector(o, mode = "any") should be TRUE whenever any of is.vector(o, mode = "<something>") is TRUE. This is not yet the case, however, see below. Consider the following examples which should be self-explaining. Besides the above bug, they also show you that -- for S compatibility -- the mode argument should really use strings as

Hello, I'm using samba 3.0.4, compiled with Kerberos 1.3.1-7, in an W2k3 ADS environment and Kerberos and the Winbind daemon are used for authentication. While checking a winbindd.log file I saw the following PANIC internal error: winbindd.log ========= [2004/07/21 12:15:00, 1] nsswitch/winbindd_group.c:winbindd_getgroups(1032) user 'root' does not exist [2004/07/21 12:15:00, 1]

Hello, I run samba 3.0.4 on a RHL9 server. Samba is a domain member of a W2k3 ADS and I use CUPS as printing mechanism; therefore Samba is compiled with Kerberos 1.3.1-7 and cups-devel. 3.0.4 runs pretty good, printing via CUPS runs well too, only the following messages I see constantly (this flooding my logs) while using 3.0.4: winbindd.log ========= [2004/07/27 16:07:04, 1]

In case it hasn't been posted before, here's instructions to get the correct time to show up on your Grandstream GXP-2000's: 1. Login to phone 2. Go to Basic Settings tab 3. Change Daylight Savings Time to yes 4. Change Optional Rule to 3,2,7,2,0;11,1,7,2,0;60 (this means change clocks the second sunday of March and back again the first sunday of November - i.e., the new savings

Dear List, With regard to the question I previously raised, here is the result I obtained right now, brglm() does help, but there are two situations: 1) Classifiers with extremely high AIC (over 200), no perfect separation, coefficients converge. in this case, using brglm() does help! It stabilize the AIC, and the classification power is better. Code and output: (need to install package:

Below is a patch to get rid of several warnings which occur while building syslinux 3.07 with the current gcc 4 snapshot. This fixes all the warnings except one unused variable. Take them or leave them as you see fit. They're all com32 stuff that's pulled in from external sources. --- syslinux-3.07/memdisk/unzip.c.gcc4 2004-12-07 23:29:22.000000000 -0500 +++

Last week I started to sketch out what would be involved in building a calendar app in Rails. In the process I went looking for what Ruby has in the way of Date/Time libraries, and in particular TimeZone support. Was (pleasantly?) surprised to find that Rails seems to have Ruby''s best timezone support. But it looks like it has a very serious bug, it isn''t daylight saving

Hi, a small question.. I'm using NTP to synch our phones with an ntp server, but it seems the Cisco 7912G (with SIP image) does not handle daylight savings time very well? Am I overlooking something or is this a known feature? I'm using GMT+1 and minutes are correct but it doesn't respect DST. SIP software seems to be: v1.02.00(040406A). Cheers, Kristof.

Since we've had discussion about DST on polycom I thought I'd pass along the rule I used to configure DST on my sipura units as well (This way the date and time passed in caller ID will be correct). Under the admin view go to the regional tab. At the bottom under miscellaneous enter this in "Daylight Saving Time Rule:" start=3/8/7/2:0:0;end=11/1/7/2:0:0;save=1 This is based

Hi, since the start of the daylight savings time my server has a problem with the log files. Sunday night the log files get rotated correctly, i.e. /var/log/messages gets /var/log.messages.1, /var/log/messages.1 get /var/log/messages.2, ... The problem now is that after log rotation new messages do no go to /var/log/messages, but to the rotated file. As DST started 3 weeks, the latest log entries

Hi all, last sunday, we went to daylight savings time here in Paris, France. All PCs moved the clock an hour forward at the boot on monday, our Solaris 2.5 system also changed the time correctly. What we observe now is that when PC clients create files on the Unix filesystem using Samba, the timestamp of the Unix file is correct when I look at it under Solaris, but there is 1 hour difference

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

Tomorrow morning my Central Europe will try to steal an hour of daylight by adding an extra hour at 2 am. This event will reintroduce an old but trivial show-stopper for the broader use of Samba. Microsoft has, perhaps intentionally, redefined the summer/winter time reckoning and just acknowledged in a KB article that, yes, MS Windows don't show the correct time, but they show the wrong

Hi, For a project I try to keep everything in normal time, not daylight saving time, to prevent problem when instruments collected data during the nights when we go from DST to normal time. But sometimes R tricks me and I do not know how to prevent it. This is one example: lights_on = as.POSIXct(c("2011-05-06 04:09:26", "2011-05-07 04:07:53", "2011-05-08

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

I've installed 1.0.r4 -- yes, it's kind of old, but seems to be the latest binary available for FreeBSD 7 -- and it doesn't want to run a setup.exe from the floppy drive. $ rm -rf .wine $ wine a:setup.exe wine: created the configuration directory '/home/perryh/.wine' wineserver: fcntl /tmp/.wine-105/server-53-772d/lock : Invalid argument $ wine 'a:\setup.exe'

Description of Problem We are rapidly approaching the time of year when some will transition from standard time (ST) to daylight savings time (DST) and others will make the opposite transition. These vernal and autumnal transitions have important implications for those with Microsoft systems and use utilities that compare file timestamps on different filesystem types or with filesystems on other