search for: exitcodes

On 06/26/17 14:42, Timo Sirainen wrote: > On 26 Jun 2017, at 23.19, Marc Perkel <marc at perkel.com> wrote: >> Ever since 2.26 I haven't been able to upgrade. In fact the install locks up my server. >> >> I get into and infinite recursive loop where the config-guess program calls itself until the server locks up from overload. >> >> I'm running Centos

...lo group, is there a way to make puppet NOT return 2 if only exec{ } and notify{ } were called? Background is as follows: I''m calling puppet agent via cron on my hosts, and I want to get mails if something changes. For this, I used the exit code of "puppet agent --test --detailed-exitcodes", which should be 2 then (or 4/6 on error). Now, every stupid notify { } or exec{ } causes $? to be 2. Without notify I could live, but exec{ } (even with a failed precondition) also makes $?==2, and I need that. Is there any way around this? Thanks for any help, Torsten -- You received...

I've upgraded all my Windows servers with the new released cwRsync version, so they're all running the latest rsync now. But this version seems to ignore exitcodes, since my batchscript does not restart the job when a timeout occurs. Before, rsync did set the errorlevel on exit, so my script knew what to do then. When you just give an empty rsync command, it should also exit with an exit code (1). But the errorlevel gets set to no. 256 instead. That could...

https://bugzilla.netfilter.org/show_bug.cgi?id=1340 Bug ID: 1340 Summary: nft -f rules.nft exitcode 1 when file too large Product: nftables Version: unspecified Hardware: x86_64 OS: Gentoo Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at netfilter.org

.... I would expect, if it can''t create the pid file, that it would exit non-zero. However, it seems to exit zero. Is there any way to change this? I''d like to know if it couldn''t run, and it seems that this is an error. [root@db1r1 ~]# puppet agent --onetime --detailed-exitcodes [root@db1r1 ~]# puppet agent --onetime --detailed-exitcodes Could not prepare for execution: Could not create PID file: /var/run/puppet/agent.pid [root@db1r1 ~]# echo $? 0 Any thoughts? -Stephanie -- You received this message because you are subscribed to the Google Groups "Puppet Users&quo...

Here is Richard's W.M. Jones answer: > This is caused by a bug in the way that supermin created symlinks > which is not compatible with the new kernel: > > 291 l bzfgrep 120777 6 0:0 -> \x1c\v > > You need to upgrade to the new supermin which fixes this. > https://www.redhat.com/archives/libguestfs/2017-July/msg00089.html >

2018-01-23 13:31 GMT+02:00 James Cook <james.cook@bluewin.ch>: > libguestfs: trace: get_cachedir > libguestfs: trace: get_cachedir = "/var/tmp" > libguestfs: [00000ms] begin building supermin appliance > libguestfs: [00000ms] run supermin > libguestfs: command: run: /usr/bin/supermin > libguestfs: command: run: \ --build > libguestfs: command: run: \ --verbose

Split most of the code from external_command to a new external_command_code, so it is possible to get the exit code of the process without considering it fatal. --- common/mltools/tools_utils.ml | 22 ++++++++++------------ common/mltools/tools_utils.mli | 8 ++++++++ 2 files changed, 18 insertions(+), 12 deletions(-) diff --git a/common/mltools/tools_utils.ml b/common/mltools/tools_utils.ml

This is still broken in the 2.2.32 release candidate. config.guess forks copies till the server dies. Running Centos 6.6 under OpenVZ. On 06/26/17 16:03, Marc Perkel wrote: > > > On 06/26/17 14:42, Timo Sirainen wrote: >> On 26 Jun 2017, at 23.19, Marc Perkel <marc at perkel.com> wrote: >>> Ever since 2.26 I haven't been able to upgrade. In fact the install

> + > +/* The exitcode is in native SVM/VMX format. The forced exitcode > + * is in generic format. > + */ Introducing a 3rd format of exitcode is over-complicated IMO. > +enum nestedhvm_vmexits > +nestedhvm_vcpu_vmexit(struct vcpu *v, struct cpu_user_regs *regs, > + uint64_t exitcode) > +{ I doubt about the necessary of this kind of wrapper. In single layer

This is still broken in the 2.2.32. config.guess forks copies till the server dies. Running Centos 6.6 under OpenVZ. On 06/26/17 16:03, Marc Perkel wrote: > > > On 06/26/17 14:42, Timo Sirainen wrote: >> On 26 Jun 2017, at 23.19, Marc Perkel <marc at perkel.com> wrote: >>> Ever since 2.26 I haven't been able to upgrade. In fact the install >>> locks up

Gentlepersons: A long time ago I used to be able to start R (version 2.6.1) from a Delphi 7 program and run a script by using a procedure like the following: function StartRAndWait (CommandLine : string) : Boolean; var Proc_info: TProcessInformation; Startinfo: TStartupInfo; ExitCode: longword; CreateOK : Boolean; begin Result := False; { Initialize the structures }

In case a repository of virt-builder references files (e.g. the index) that cannot be downloaded (network issues, 404, etc) then virt-builder errors out on this situation. This is not a nice situation, from an user POV. This series does some refactoring to allow to better handle downloading failures, and handle the failures gracefully in virt-builder. RFC because I'm not yet too convinced

On Wed, Jan 16, 2019 at 03:17:32PM +0100, Pino Toscano wrote: > Split most of the code from external_command to a new > external_command_code, so it is possible to get the exit code of the > process without considering it fatal. > --- > common/mltools/tools_utils.ml | 22 ++++++++++------------ > common/mltools/tools_utils.mli | 8 ++++++++ > 2 files changed, 18

Hi, I'm experimenting with using LLVM to generate dynamic FFI bridges in VisualWorks Smalltalk. LLVM is an amazing thing! I'm going from dynamically generated assembler source to machine code, and I have that all working, copied from the llc tool and the JIT example. I have two questions: 1. What optimization passes, if any, should I run on the module before I pass it to the

Ever since 2.26 I haven't been able to upgrade. In fact the install locks up my server. I get into and infinite recursive loop where the config-guess program calls itself until the server locks up from overload. I'm running Centos 6 under OpenVZ. What am I missing? I think there's a serious bug. 31233 pts/3 S 0:00 /bin/sh ./config.guess 31235 pts/3 S 0:00 \_

This happens with GCC 7.0.1. The errors were all of the form: qemu-speed-test.c: In function 'main': qemu-speed-test.c:153:7: error: this statement may fall through [-Werror=implicit-fallthrough=] usage (EXIT_SUCCESS); ^~~~~~~~~~~~~~~~~~~~ qemu-speed-test.c:155:5: note: here default: ^~~~~~~ --- builder/index-validate.c | 2 +-

When we are valgrinding we don't really care about the child processes, which might be qemu, libvirtd, etc. So disable tracing into children (at least, as far as is possible with valgrind, which is not entirely disabling it, but suppressing it). --- m4/guestfs_progs.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/m4/guestfs_progs.m4 b/m4/guestfs_progs.m4 index