Displaying 20 results from an estimated 117 matches for "50.000000000".
Did you mean:
10.000000000
2005 Jul 31
1
BUG: Standard Time v. DST calculated wrong by Samba Server
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"
2005 Jul 30
0
Samba bug: 1 out of 387 files off by 1 hour (DST/ST bug)
Summary:
There appears to be a bug in the "time range" Samba is using on
dates where time is scheduled to "Spring Forward" from Standard
to Daylight Savings time. Might want to review the code for
"Falling back", as well...
Details:
This started out with my thinking it was an rsync problem, but
it appears to be something to do with how samba is exporting the
file
2005 Mar 07
0
gcc4 warnings
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
+++
2011 Jun 21
13
VM disk I/O limit patch
Hi all,
I add a blkback QoS patch.
You can config(dynamic/static) different I/O speed for different VM disk
by this patch.
----------------------------------------------------------------------------
diff -urNp blkback/blkback.c blkback-qos/blkback.c
--- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800
+++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800
@@ -44,6 +44,11 @@
2011 Jun 21
13
VM disk I/O limit patch
Hi all,
I add a blkback QoS patch.
You can config(dynamic/static) different I/O speed for different VM disk
by this patch.
----------------------------------------------------------------------------
diff -urNp blkback/blkback.c blkback-qos/blkback.c
--- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800
+++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800
@@ -44,6 +44,11 @@
2004 Feb 02
1
Bug in mbr.asm
Found this small bug. It won't print error messages. A simple fix.
--- mbr.asm.orig 2002-10-03 06:02:50.000000000 -0400
+++ mbr.asm 2004-01-08 06:55:13.000000000 -0500
@@ -165,7 +165,7 @@
die:
.msgloop:
lodsb
- xor al,al
+ or al,al
jz .now
mov ah,0Eh ; TTY output
mov
2002 Jun 15
0
[PATCH] make test patch.
Yo,
Currently if you build rsync and you don't have rsync installed, make
test will fail because some tests reference the rsync binary directly
(instead of using the $RSYNC variable).
I cannot find anything which refers to this problem in the mail archives
or CVS logs.
Below is a patch which fixes this problem.
(please CC: me, I'm not subscribed. Thanks.)
-- Geoff.
--------------
2003 Nov 04
0
ServerLiesWarning
I'm trying to replace some sshv1 clients and servers in a modular way,
and the "Server Lies" warning (when the server says the key has one
more bit than it really has) is causing heartache. Per the FAQ, this
is relatively benign. Here's a patch that allows an admin or user to
disable the warning.
- Morty
diff -Nur openssh-3.7.1p2/readconf.c
2008 Jul 30
0
[LLVMdev] llvm-gcc fortran bootstrap broken
And how about this one so as not to include a C specific
header in llvm-backend (!!!) and not to have llvm-backend
use a C specific flag (flag_no_builtin)?
Index: gcc-4.2.llvm/gcc/c-opts.c
===================================================================
--- gcc-4.2.llvm.orig/gcc/c-opts.c 2008-07-30 21:25:28.000000000 +0200
+++ gcc-4.2.llvm/gcc/c-opts.c 2008-07-30 21:26:17.000000000 +0200
@@
2014 Sep 13
2
C5 : Deleting un-deletable files ?
During a routine trawl through the ext3 files, I found some astronomical file sizes, billions and billions of GB.
They also has strange user and group names.
I can not delete these "weird files" (the term used by the operating system utilities).
Here are a few examples. The original files were created on Windoze 98 version 2 circa 2001.
> 2411957 p--x---rwx 65487 299196551
2008 Mar 20
1
Bug#471768: there's no hvmloader in xen-utils-unstable
Package: xen-utils-unstable
Version: 3.3-unstable+hg17192-1
Severity: important
Tags: patch
In tools/firmware/Makefile, INST_DIR is $(DESTDIR)/usr/$(PREFIX)/boot
but $(PREFIX) is empty. hvmloader doesn't get installed.
diff -ru xen-unstable-3.3-unstable+hg17192.orig/debian/patches/tools-prefix.diff xen-unstable-3.3-unstable+hg17192/debian/patches/tools-prefix.diff
---
2006 Jun 15
0
[PATCH 2/2] Runtime configuration of HTB''s HYSTERESIS option (userspace)
The HTB qdisc has a compile time option, HTB_HYSTERESIS,
that trades accuracy of traffic classification for CPU
time. These patches change hysteresis to be a runtime
option under the control of "tc".
The effects of HYSTERESIS on HTB''s accuracy are significant
(see chapter 7, section 7.3.1, pp 69-70 in Jesper Brouer''s
thesis: http://www.adsl-optimizer.dk/thesis/ ),
2012 Aug 13
9
[PATCH RFC] xen/netback: Count ring slots properly when larger MTU sizes are used
Hi,
I ran into an issue where netback driver is crashing with BUG_ON(npo.meta_prod > ARRAY_SIZE(netbk->meta)). It is happening in Intel 10Gbps network when larger mtu values are used. The problem seems to be the way the slots are counted. After applying this patch things ran fine in my environment. I request to validate my changes.
Thanks
Siva
2013 Jan 25
2
[LLVMdev] [cfe-dev] RFC: put commit messages in *-commits subject lines?
Hi Daniel,
Daniel Dunbar wrote:
> Hi Sebastion,
>
> I've attached the current configuration file from the server.
>
> I'm not sure how far you want to go down the "trying to get realize nice
> summary path" lines, but if svn_mailer somehow supported running an
> external script to process the commit and come up with the path that would
> be ideal for
2012 Sep 20
2
[LLVMdev] RFC: Adding an option to llvm-link to allow it to get a list of input bitcode file names from a file
Well, although cl::ParseCommandLineOptions contains support for @file. By default it is disabled, which is the case for llvm-link.
To enable @file support in llvm-link, a small change is needed:
--- llvm-link.cpp.orig 2012-09-20 16:10:50.000000000 -0400
+++ llvm-link.cpp 2012-09-20 16:11:24.000000000 -0400
@@ -83,7 +83,7 @@
LLVMContext &Context = getGlobalContext();
2007 Apr 18
1
[PATCH 2/3] Gdt_accessor
Add an accessor function for getting the per-CPU gdt. Callee must already
have the CPU.
Signed-off-by: Zachary Amsden <zach@vmware.com>
Index: linux-2.6.14-rc1/include/asm-i386/desc.h
===================================================================
--- linux-2.6.14-rc1.orig/include/asm-i386/desc.h 2005-09-20 14:49:10.000000000 -0700
+++ linux-2.6.14-rc1/include/asm-i386/desc.h
2007 Apr 18
1
[PATCH 2/3] Gdt_accessor
Add an accessor function for getting the per-CPU gdt. Callee must already
have the CPU.
Signed-off-by: Zachary Amsden <zach@vmware.com>
Index: linux-2.6.14-rc1/include/asm-i386/desc.h
===================================================================
--- linux-2.6.14-rc1.orig/include/asm-i386/desc.h 2005-09-20 14:49:10.000000000 -0700
+++ linux-2.6.14-rc1/include/asm-i386/desc.h
2007 Apr 18
2
[PATCH 4/21] i386 Broken bios common
Both the APM BIOS and PnP BIOS code use a segment hack to simulate real
mode selector 0x40 (which points to the BIOS data area at 0x00400 in
real mode). Several broken BIOSen use selector 0x40 as if they were
running in real mode, which we make work by faking up selector 0x40 in
the GDT to point to physical memory starting at 0x400. We limit the
access to the remainder of this physical page
2007 Apr 18
2
[PATCH 4/21] i386 Broken bios common
Both the APM BIOS and PnP BIOS code use a segment hack to simulate real
mode selector 0x40 (which points to the BIOS data area at 0x00400 in
real mode). Several broken BIOSen use selector 0x40 as if they were
running in real mode, which we make work by faking up selector 0x40 in
the GDT to point to physical memory starting at 0x400. We limit the
access to the remainder of this physical page
2007 Feb 08
1
supsmu(periodic=TRUE) can crash R by reading before start of array (PR#9502)
supsmu(periodic=TRUE) can crash R by reading before start of array.
To reproduce:
set.seed(1)
xx <- runif(29000)
yy <- rnorm(29000)
span <- 0.49
i <- 1
while(i < 200){
cat(i,"\n")
int <- supsmu(xx,yy,periodic=T,span=span)
i <-i+1
}
results in:
1
2
3
4
5
6
7
8
9
Program received signal SIGSEGV,