search for: timeformat

...ir = .logData) | | assign("logToConsole", TRUE, envir = .logData) | ## | assign("logHeaderLevel", 0, envir = .logData) | assign("logHeader", "", envir = .logData) | assign("logHeaderClock", "", envir = .logData) | assign("timeFormat", "", envir = .logData) `---- to initialize some logging parameter. When I load my package, everything looks fine, only that the environment logger:::.logData is (nearly) empty: ,---- | > library(logger) | > ls(envir=logger:::.logData, all.names=TRUE) | [1] ".logHeader&...

...orse than the stable binaries > for 3.2 > > I've used: > http://llvm.org/releases/3.2/clang+llvm-3.2-x86_64-linux-ubuntu-12.04.tar.gz > vs > http://llvm.org/pre-releases/3.3/rc3/clang+llvm-3.3rc3-Ubuntu-12.04.2-x86_64.tar.gz > > On a simple hello.c file: > /ssd/bench$ TIMEFORMAT="%E" > /ssd/bench$ for I in `seq 1 5`; do \ > time /ssd/llvm3.2/bin/clang -c hello.c; \ > done > 0.015 > 0.014 > 0.013 > 0.013 > 0.013 > > /ssd/bench$ for I in `seq 1 5`; do \ > time /ssd/llvm3.3rc/bin/clang -c hello.c; \ > done > 0.992 >...

...rtup performance of your binaries is much worse than the stable binaries for 3.2 I've used: http://llvm.org/releases/3.2/clang+llvm-3.2-x86_64-linux-ubuntu-12.04.tar.gz vs http://llvm.org/pre-releases/3.3/rc3/clang+llvm-3.3rc3-Ubuntu-12.04.2-x86_64.tar.gz On a simple hello.c file: /ssd/bench$ TIMEFORMAT="%E" /ssd/bench$ for I in `seq 1 5`; do \ time /ssd/llvm3.2/bin/clang -c hello.c; \ done 0.015 0.014 0.013 0.013 0.013 /ssd/bench$ for I in `seq 1 5`; do \ time /ssd/llvm3.3rc/bin/clang -c hello.c; \ done 0.992 0.978 0.982 0.981 0.976 Is this an expected behaviour (e.g. +Asserts...

Hi LLVM-ites! We are doing a quick test of 3.3rc3. Our testers did a quick turn around and created binaries which you can test. Please give them a go and let us know how they work for you. They are here: http://llvm.org/pre-releases/3.3/rc3 We don't have a lot of time remaining in the release cycle, so please do whatever you can to make sure they are solid. In particular, make sure that

...for 3.2 >> >> I've used: >> http://llvm.org/releases/3.2/clang+llvm-3.2-x86_64-linux-ubuntu-12.04.tar.gz >> vs >> http://llvm.org/pre-releases/3.3/rc3/clang+llvm-3.3rc3-Ubuntu-12.04.2-x86_64.tar.gz >> >> On a simple hello.c file: >> /ssd/bench$ TIMEFORMAT="%E" >> /ssd/bench$ for I in `seq 1 5`; do \ >> time /ssd/llvm3.2/bin/clang -c hello.c; \ >> done >> 0.015 >> 0.014 >> 0.013 >> 0.013 >> 0.013 >> >> /ssd/bench$ for I in `seq 1 5`; do \ >> time /ssd/llvm3.3rc/bin/clang...

...ed: > >> > http://llvm.org/releases/3.2/clang+llvm-3.2-x86_64-linux-ubuntu-12.04.tar.gz > >> vs > >> > http://llvm.org/pre-releases/3.3/rc3/clang+llvm-3.3rc3-Ubuntu-12.04.2-x86_64.tar.gz > >> > >> On a simple hello.c file: > >> /ssd/bench$ TIMEFORMAT="%E" > >> /ssd/bench$ for I in `seq 1 5`; do \ > >> time /ssd/llvm3.2/bin/clang -c hello.c; \ > >> done > >> 0.015 > >> 0.014 > >> 0.013 > >> 0.013 > >> 0.013 > >> > >> /ssd/bench$ for I in `seq 1...

...result"><ERRORCODE>0</ERRORCODE><PRODUCT BUILD="9/10/2003" NAME="FileMaker Pro Web Companion" VERSION="6.0v2"/ ><DATABASE DATEFORMAT="d-M-yyyy" LAYOUT="XMLDump" NAME="Customers.fp5" RECORDS="26" TIMEFORMAT="k:mm:ss"/ ><METADATA><FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="Company" TYPE="TEXT"/><FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="Street" TYPE="TEXT"/><FIELD EMPTYOK="YES" M...

...context=office ; extension=line rtp_method=1 maintext0="GREETING" ; default = "Welcome", 24 characters max maintext1="have a great day" ; default = the name of the device, 24 characters max dateformat=1 ; 0 = month/day, 1 (default) = day/month timeformat=2 ; 0 = 0:00am ; 1 (default) = 0h00, 2 = 0:00 callhistory=0 ; 0 = disable, 1 = enable call history, default = 1 [group3] callgroup = 3 pickupgroup = 3 [group4] callgroup = 4 pickupgroup = 4 [group5] callgroup = 3,5 pickupgroup = 3,5 [group6] callgroup = 6...

Hi, isn?t this weird: # time foo real 43m39.841s user 15m31.109s sys 0m44.136s Almost 30 minutes have disappeared, but it actually took about that long, so what happened?

Right-- I've seen the Avaya document you cite below. It says "To administer DHCP option 242, make a copy of an existing option 176" but I don't have any example of option 176 or 242 to copy, and don't know what to do to /etc/dhcpd.conf to make it offer option 242. Then there's this long table of parameters to use with (presumably) option 242. I was hoping someone had a

[TOP lINE: is there a linux program that will tell me where all the installed files went?] Hi all....great to be here... i''m pretty relentless yet very new to RoR and fairly new to Linux [went with ubuntu 7.10 for the time being - learing pure Deb and/or Slack/BDS for the future] anyhooo.. So... Coming from my highly understood XP install [frankly it feels yuk these days] i''m

...s.sh +set -e +set -x + +requires qemu-img --version + +files="rate.img rate.time rate.err" +rm -f $files +cleanup_fn rm -f $files + +# This should take no less than 20 seconds to run: +# (8 * 25 * 1024 * 1024) / (10 * 1024 * 1024) = 20 + +# We are using the bash time builtin, so setting TIMEFORMAT will +# control the output format of the time builtin. For strange use of +# { ; } here, see: https://stackoverflow.com/a/13356654 +set +x +{ TIMEFORMAT="%0R" ; time nbdkit --filter=rate memory size=25M rate=10M --run 'qemu-img convert -p $nbd rate.img' 2>rate.err ; } 2>rat...

For virt-v2v we have been discussing how to limit network bandwidth. The initial discussion has been around how to use cgroups to do this limiting, and that is still probably what we will go with in the end. However this patch gives us another possibility for certain virt-v2v inputs, especially VDDK. We could apply a filter on top of the nbdkit plugin which limits the rate at which it copies