search for: stderrors

Displaying 20 results from an estimated 36 matches for "stderrors".

Did you mean: stderror
2016 Jan 21
0
[PATCH v3 2/6] daemon: Split out command() functions and CLEANUP_* macros into separate files.
Allows more sharing between the daemon and the inspection program. --- daemon/Makefile.am | 2 + daemon/cleanups.c | 80 ++++++++++ daemon/cleanups.h | 47 ++++++ daemon/command.c | 436 +++++++++++++++++++++++++++++++++++++++++++++++++++++ daemon/command.h | 41 +++++ daemon/daemon.h | 47 +----- daemon/guestfsd.c | 392 ----------------------------------------------- po/POTFILES
2016 Jan 26
1
[PATCH] daemon: improve debugging for "stdout on stderr" flag
When the COMMAND_FLAG_FOLD_STDOUT_ON_STDERR flag is passed to command*(), indicate that as stdout=e in debugging message. --- daemon/command.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/daemon/command.c b/daemon/command.c index 73fce56..2423a4e 100644 --- a/daemon/command.c +++ b/daemon/command.c @@ -185,6 +185,7 @@ commandrvf (char **stdoutput, char **stderror,
2012 Dec 13
2
[PATCH 1/2] daemon: NFC Use symbolic names in commandrvf
Improve readability of commandrvf() by replacing bare int values for file descriptors with their symbolic names STD{IN,OUT,ERR}_FILENO. Also add PIPE_READ and PIPE_WRITE for referencing relevant ends of a pipe. --- daemon/guestfsd.c | 79 +++++++++++++++++++++++++++++-------------------------- 1 file changed, 42 insertions(+), 37 deletions(-) diff --git a/daemon/guestfsd.c b/daemon/guestfsd.c
2012 Dec 14
1
[PATCH] daemon: Add sentinel attribute to commandf and commandrf
Causes a compiler warning to be emitted if you omit the trailing NULL argument. --- daemon/daemon.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/daemon/daemon.h b/daemon/daemon.h index 8f932d2..df1ba3a 100644 --- a/daemon/daemon.h +++ b/daemon/daemon.h @@ -100,9 +100,9 @@ extern char **split_lines (char *str); #define COMMAND_FLAG_CHROOT_COPY_FILE_TO_STDIN 2048
2009 Nov 09
1
[PATCH libguestfs] indent with spaces, not TABs
One more after this, and "make syntax-check" will pass once more. >From 5c360133c0d4e09531d432abca0629798b87ff39 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Mon, 9 Nov 2009 15:14:53 +0100 Subject: [PATCH libguestfs] indent with spaces, not TABs * HACKING: Expand indentation TABs. * configure.ac: Likewise. * daemon/daemon.h: Likewise. *
2009 Nov 08
1
Summary methods
I've defined the following for objects of a class called jml summary.jml <- function(object, ...){ tab <- cbind(Estimate = coef(object), StdError = object$se, Infit = object$Infit, Outfit = object$Outfit) res <- list(call = object$call, coefficients = tab, N = nrow(object$Data), iter = object$Iterations) class(res) <- "summary.jml" res }
2003 Dec 10
3
How to calculate standard error for a vector?
Hi all! I 'm beginner and i develop a bio-application with VB and i need some statistic functions! could i calculate StdError, CoeffOfVariance, SumSquared with R langage? if yes, what are functions to use? I need also to use ANOVA and t-test... Thanks for your help! Laurent Houdusse Analyste Programmeur
2011 Jun 09
15
[PATCH 00/13] Fix errors found using Coverity static analyzer.
I ran the Coverity static analyzer[1] on libguestfs, and fixed many errors as a result. Coverity found some errors in gnulib, but it doesn't seem to be worth following those up since the version of gnulib we are using is so old. There are a couple more errors (possibly 1 false-positive) which I'm going to send in a separate email. BTW all the errors found by Coverity were in the daemon
2009 Aug 17
13
total warning-removal for daemon/
The warnings in daemon were aggravating and risky for development (too easy to miss new ones) so I spent some time last week and today working on removing them. The first patch gets us down to almost no warnings with the original -Wall setting. That was by far the hardest part. Once I'd done that, I enabled nearly all of gcc's warnings via gnulib's warnings and manywarnings modules
2016 Jan 21
8
[PATCH v3 0/6] [FOR COMMENTS ONLY] Rework inspection.
For background on this change, see: https://rwmj.wordpress.com/2015/12/06/inspection-now-with-added-prolog/ v2 was previously posted here: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html To test this patch series on a real guest, you can do: $ ./run guestfish -v -x -a /var/tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection
2015 Dec 05
6
[PATCH 0/6 v2] [FOR COMMENTS ONLY] Rework inspection.
This is a more working version. Inspection (partially) succeeds on a real guest this time :-) You can test it out on a real guest (in this case, a CentOS disk image located at /tmp/centos-6.img) by doing: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" which will print lots of debugging, and at the end the
2015 Dec 02
3
[PATCH] daemon: improve internal commandrvf
- add a flag to request chroot for the process, which is done only as very last (before chdir) operation before exec'ing the process in the child: this avoids using CHROOT_IN & CHROOT_OUT around command* invocations, and reduces the code spent in chroot mode - add failure checks for dup2 and open done in child, not proceeding to executing the process if they fail - open /dev/null
2002 Mar 22
3
heteroskedasticity-robust standard errors
I am trying to compute the white heteroskedasticity-robust standard errors (also called the Huber standard errors) in a linear model, but I can't seem to find a function to do it. I know that the design library in S+ has something like this (robcov?), but I have not yet seen this library ported to R. Anyone know if there is already a function built into R to do this relatively simple job?
2001 Jul 06
2
winelib and compiling MFC
Hi, The company I work for, has asked me to use winelib to port some code, however I have a problem compiling the MFC. I run winemaker 0.5.7 with options: 'winemaker --lower-uppercase -nomfc --dll ./ > \ winemaker_output.txt' No errors in file or stderror; further winemaker accesses the correct directories. But when I run ./configure as: './configure --with-wine=/usr/bin \
2023 Jun 05
1
error in arfima...
Dear Martin, Sad that the bug is beyond your ken... Fortunately, the error happens only rarely...The length of LYGH was 719 and there were only two such errors..I will just replace them with NA and make do. By the by, what if I send LYGH as an attachment to your actual mail ( not the r-help mail)? Will it help? Can you then pinpoint the cause? Or should I raise a bug
2023 Jun 01
1
error in arfima...
>>>>> akshay kulkarni >>>>> on Wed, 31 May 2023 20:55:33 +0000 writes: > dear members, > I am using arfima() from forecast package to model a time > series. The following is the code: >> LYGH[[202]] > [1] 45.40 3.25 6.50 2.15 >> arfima(LYGH[[202]]) > Error in .fdcov(x, fdf$d, h, nar = nar, nma = nma,
2015 Jun 17
0
[PATCH 4/4] daemon: add split_lines_sb
Mold split_lines_sb from split_lines, so it returns the strings buffer with the result of the split. This way, we can have the number of lines in the array, with no need to count them again later. split_lines is rewritten to take the ownership of the result of split_lines_sb. --- daemon/daemon.h | 1 + daemon/guestfsd.c | 37 ++++++++++++++++++++++++++++--------- 2 files changed, 29
2006 Jul 19
1
fracdiff
Hi, I'm using the function fracdiff and can not figure out how to get the estimated values for sigma2 or confidence intervals for the parameter estimates. Does anyone know how to obtain these values? Thanks, Melissa
2010 Nov 23
1
redirecting time output
Hi, am trying to pipe output from time command and output from a shell script to the mail program. So far it's not working as expected... # time echo "test" 2>&1 | mail -s "timetest" my at mail.com real 0m0.126s user 0m0.000s sys 0m0.000s The time command writes to stderror, but here the redirection seems to apply to the echo command? Thx Rainer
2012 Mar 13
2
[PATCH 0/2] 'int' to 'size_t' changes
These two patches are probably not completely independent, but separating them is a lot of work. With *both* patches applied, all the tests and extra-tests pass. That's no guarantee however that there isn't a mistake, so I don't think this patch is a candidate for the 1.16 branch, until it's had a lot more testing in development. Rich.