search for: l60

...er" declaration is being parsed. upsdrvctl just passes arguments to the drivers via the command line (including "-u", although that is not read from the configuration file, but from upsdrvctl's command line). https://github.com/networkupstools/nut/blob/master/drivers/upsdrvctl.c#L60 I'm quite sure that it is the place where the config file is parsed... And the init script of the debian package don't explicitly append "-u nut" in wheezy. See the attached patch in my first message. > Can you show us the exact configuration syntax you are using? 8<----...

...rprising in the configure log: > -- No build type selected, default to Debug It appears that llvm's configuration forces Debug builds if the user does not specify the build type. https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 I've just done a build of llvm and clang 10 in debug mode for X86 and ARM targets and it weighs in at a whopping 75GiB. I feel that forcing Debug builds in the absence of an option to be a wasteful default. It is a valid and useful thing to call cmake without specifying a build type; absence o...

...lity with the current behavior? I'm aware of workarounds, I just prefer xtabs() over table() for its interface. Thanks. Best regards Kirill [1] http://rpubs.com/krlmlr/xtabs-NA [2] https://github.com/wch/r-source/blob/780021752eb83a71e2198019acf069ba8741103b/src/library/stats/R/xtabs.R#L60 data <- factor(letters[1:4], levels = letters[1:3]) data ## [1] a b c <NA> ## Levels: a b c xtabs(~data) ## data ## a b c ## 1 1 1 xtabs(~data, na.action = na.pass) ## data ## a b c ## 1 1 1 xtabs(~data, na.action = na.pass, exclude = numeric()) ## data ## a b c ## 1 1 1 xtabs(~...

Hi, I'm using libguestfs 1.42, When I run the following python3 commands on a rhel7.8: print(g.ls('/sys')) print(g.sh('ls /sys')) I get: [] block bus class dev devices firmware fs hypervisor kernel module power It seems that g.ls('/sys') is chrooted correctly. But g.sh('ls /sys') isn't. I came across this behavior when I used

...build type selected, default to Debug >> >> It appears that llvm's configuration forces Debug builds if the user >> does not specify the build type. >> >> https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 >> >> I've just done a build of llvm and clang 10 in debug mode for X86 and >> ARM targets and it weighs in at a whopping 75GiB. I feel that forcing >> Debug builds in the absence of an option to be a wasteful default. It is >> a valid and useful thing to call cmak...

...ces > firmware > fs > hypervisor > kernel > module > power sh bind-mounts /sys from the appliance into the filesystem temporarily in order to make it possible to run some commands: https://github.com/libguestfs/libguestfs/blob/fce82fe55a2b64a1a7e494858aa272d608e5e54e/daemon/sh.c#L60 However this /sys has nothing to do with /sys as it may appear in the guest when it is running. Libguestfs edits filesystems, it doesn't run the guest. > It seems that g.ls('/sys') is chrooted correctly. > But g.sh('ls /sys') isn't. > > I came across this beh...

Hi. I would like to share with you my experience on trying to use nut with a Liebert GXT3 on a Debian wheezy with nut-server 2.6.4. Please find my observations below. (1) I've installed the packaged version of nut-server # aptitude install nut-server (2) I did some tuning for my configuration #??cat << EOF >> /etc/nut/ups.conf user=nut [liebert] ??????? driver=usbhid-ups

...t; >> -- No build type selected, default to Debug > > It appears that llvm's configuration forces Debug builds if the user > does not specify the build type. > > https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 > > I've just done a build of llvm and clang 10 in debug mode for X86 and > ARM targets and it weighs in at a whopping 75GiB. I feel that forcing > Debug builds in the absence of an option to be a wasteful default. It is > a valid and useful thing to call cmake without specifyin...

...t; > > -- No build type selected, default to Debug > > It appears that llvm's configuration forces Debug builds if the user > does not specify the build type. > > > https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 > > I've just done a build of llvm and clang 10 in debug mode for X86 and > ARM targets and it weighs in at a whopping 75GiB. I feel that forcing > Debug builds in the absence of an option to be a wasteful default. It is > a valid and useful thing to call cmake without specifying...

...gt; > > -- No build type selected, default to Debug > > It appears that llvm's configuration forces Debug builds if the user > does not specify the build type. > > https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 > > I've just done a build of llvm and clang 10 in debug mode for X86 and > ARM targets and it weighs in at a whopping 75GiB. I feel that forcing > Debug builds in the absence of an option to be a wasteful default. It is > a valid and useful thing to call cmake without specifying...

...wrote: >> -- No build type selected, default to Debug > It appears that llvm's configuration forces Debug builds if the user > does not specify the build type. > > https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 > > I've just done a build of llvm and clang 10 in debug mode for X86 and > ARM targets and it weighs in at a whopping 75GiB. I feel that forcing > Debug builds in the absence of an option to be a wasteful default. It is > a valid and useful thing to call cmake without specifyin...

...build type selected, default to Debug >> >> It appears that llvm's configuration forces Debug builds if the user >> does not specify the build type. >> >> https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 >> >> I've just done a build of llvm and clang 10 in debug mode for X86 and >> ARM targets and it weighs in at a whopping 75GiB. I feel that forcing >> Debug builds in the absence of an option to be a wasteful default. It is >> a valid and useful thing to call cmak...

...ion is being parsed. upsdrvctl just passes arguments to the drivers via the command line (including "-u", although that is not read from the configuration file, but from upsdrvctl's command line). >> >> https://github.com/networkupstools/nut/blob/master/drivers/upsdrvctl.c#L60 >> >> I'm quite sure that it is the place where the config file is parsed... > > What I should have said is that upsdrvctl is not where the "user = " is being interpreted (although you are correct, it is parsed and ignored). I was thinking of this line in the driver...

...sor > > kernel > > module > > power > > sh bind-mounts /sys from the appliance into the filesystem temporarily > in order to make it possible to run some commands: > > https://github.com/libguestfs/libguestfs/blob/fce82fe55a2b64a1a7e494858aa272d608e5e54e/daemon/sh.c#L60 > > However this /sys has nothing to do with /sys as it may appear in the > guest when it is running. Libguestfs edits filesystems, it doesn't > run the guest. Yes, I understand that, I am just surprised to know that we bind /sys for g.sh() commands. However, "g.command([sel...

More complete documentation below. Rich. ---------------------------------------------------------------------- libguestfs on Mac OS X (tested with libguestfs-1.23.33): -------------------------------------------------------- prerequisites: -------------- - install osxfuse, download from: http://osxfuse.github.io - install some dependencies using macports: sudo port install qemu cdrtools pcre

...(c) Copyright 1994-97, NCR Corporation (c) Copyright 1987-97, MetaWare Incorporated cc -I. -I. -g -DHAVE_CONFIG_H -I./popt -c hlink.c -o hlink.o NCR High Performance C Compiler R3.0c (c) Copyright 1994-97, NCR Corporation (c) Copyright 1987-97, MetaWare Incorporated w "hlink.c",L60/C8(#257): '=' encountered where '==' may have been intended. No errors 1 warning cc -I. -I. -g -DHAVE_CONFIG_H -I./popt -c token.c -o token.o NCR High Performance C Compiler R3.0c (c) Copyright 1994-97, NCR Corporation (c) Copyright 1987-97, MetaWare Incorporated...

...ur commits from here [6] https://reviews.llvm.org/D67500 , I probably should push to land this [7] It's not a bad view, and definitely something I've been preaching, [8] https://github.com/jmorse/llvm-project/blob/11450def5bc592321ece2a64ea2a8cabbc614c39/llvm/lib/CodeGen/LiveDebugValues.cpp#L60 -- Thanks for reading this essay, Jeremy