search for: exitted

There's a new syntax check rule from gnulib. It requires that you write e.g., exit (EXIT_SUCCESS), not exit (0). And the same for 1/EXIT_FAILURE and any other constants. There were a lot of violations, including a few false positives, so I started with the exemptions (see the .x-sc file below). Then I converted the vast majority automatically, with this: maint: use EXIT_SUCCESS and

Why does the following eval() call on sys.on.exit() not return what I expect/evaluate in the proper environment? foo <- function() { cat("foo()...\n"); on.exit( message("exiting") ) cat("sys.on.exit():\n") res <- sys.on.exit() print(res) cat("eval(sys.on.exit()):\n") expr <- quote(sys.on.exit()) print(expr) res <- eval(expr)

I have encountered a 'strange' behavior in the 'on.exit' processing. I had a function where I setup an 'on.exit' condition and then later on added to it with an 'on.exit({...}, add=T)'. What appeared to happen is that on subsequent calls to the function, even if only the first 'on.exit' was called, it was still executing the one with the 'add=T'.

Hello Folks, I have used FreeBSD-4.8-RC and apache 1.3.2x. In some days,my dmesg has shown as the lines; pid 9229 (httpd), uid 80: exited on signal 11 pid 10106 (httpd), uid 80: exited on signal 11 pid 9842 (httpd), uid 80: exited on signal 11 pid 35708 (httpd), uid 80: exited on signal 11 pid 9371 (httpd), uid 80: exited on signal 11 pid 10337 (httpd), uid 80: exited on

Hi all, I really don't know where to go from here. I've traced and pasted, but never heard responses.... I'm getting the following (see bottom of this email) in a single day of dmesg....most of the time the error message in the log file is something like: Oct 5 09:21:43 mail1 dovecot: imap(*****): file mbox-save.c: line 280 (mbox_save_init_file): assertion failed:

I am writing a small ruby script that will be accepting input from postfix''s pipe command (ie, not running via the shell, directly executing). One of the things I need to do it spec the exit codes to make sure I am returing the correct exit codes for each condition as Postfix will then return SMTP errors as appropriate. I have two files that concern this bit of the program, init.rb and

I have a funny issue whereby when a application exits the proc:::exit probe doesn''t seem to be firing. A customer has written a dtrace script that outputs some info whenever proc:::exit fires but on occasion (random, no pattern in behaviour) dtrace exits without outputting the data. They are running dtrace via ''dtrace -s exit_trace.d -p <pid>'' Can anyone think

Thanks: Eric Blake for the suggestion here: https://www.redhat.com/archives/libguestfs/2018-September/msg00069.html --- tests/functions.sh.in | 25 +++++++++++++++++++++++++ tests/test-blocksize.sh | 9 ++------- tests/test-cache.sh | 9 ++------- tests/test-cow.sh | 9 ++------- tests/test-data-7E.sh | 9

This incomplete patch adds a new filter allowing more control over when nbdkit exits. You can now get nbdkit to exit gracefully on certain events, such as a file being created, a pipe held open by another process going away, or when another PID exits. There is also a script option to allow for completely custom events. It is untested at the moment, I'm posting it to get feedback on the

The following example involves a function whose on.exit() expression both generates an error and catches the error. The body of the function also generates an error. When calling the function wrapped in a tryCatch, should that tryCatch's error function be given the error from the body of the function, since the one from the on.exit has already been dealt with? Currently the outer tryCatch

Hi, all Stupid question, but how do you exit asterisk console without stopping the asterisk? Tried quit and exit: *CLI> exit No such command 'exit' (type 'help' for help) *CLI> quit No such command 'quit' (type 'help' for help) *CLI> Any other ideas? I started asterisk with -cvvvvg option. Same problem if use asterisk -r to connect. Can not exit. Any

CentOS 6 has libguestfs-devel 1.20.11, which predates the support in guestfs_add_drive_opts() for requesting an nbd drive instead of a local file. The guestfs plugin can still be built, so no configure changes are needed; but skip the tests that fail to compile so that 'make check' can at least complete. Signed-off-by: Eric Blake <eblake@redhat.com> --- Even with this patch,

Here's a fun spin on this same topic (I can't file a bug at this moment since llvm.org is down). Consider: define i32 @x(i32* %x, i1* %y) { entry: br label %loop loop: %v = phi i32 [ 0 , %entry ], [ %v.inc, %exit.inner ], [ %v, %loop ] %c = load volatile i1, i1* %y br i1 %c, label %exit.inner, label %loop exit.inner: %c1 = load volatile i1, i1* %y %x.val = load i32, i32*

I was able to get it to compile but the tests are failing. When I run the test as root I get: run test connect.sh ... Connection closed by 127.0.0.1 ssh connect with protocol 1 failed failed simple connect make[1]: *** [t-exec] Error 1 make: *** [tests] Error 2 However, when I run as a normal user I got: test remote exit status: proto 1 status 0

--- docs/nbdkit-captive.pod | 6 +- docs/nbdkit-service.pod | 1 + filters/exitlast/nbdkit-exitlast-filter.pod | 3 + filters/exitwhen/nbdkit-exitwhen-filter.pod | 156 ++++++ filters/ip/nbdkit-ip-filter.pod | 1 + filters/limit/nbdkit-limit-filter.pod | 1 + filters/rate/nbdkit-rate-filter.pod | 1 +

Here is an executable that would allow a user to change the linux and SMB passwords simultaneously. The website indicated in the comments had some problems in the code, but they are fixed in the cpasswd.c file which is below and also attached. Hope that this helps others. The code is a fix, not a solution. it only works from the command prompt, but it helps with keeping linyx and Samba

Hi, I recently updated to R 3.0.1. I'm running linux ubuntu 12.04. I realized that I have to update all the installed packages so I run > update.packages(checkBuilt=TRUE) as described here http://www.r-bloggers.com/r-3-0-0-is-released-whats-new-and-how-to-upgrade/ . The first thing it did was telling me that it will not update several packages. When it was finished I used the warnings

Wherever we had code which did: if (something_bad) { perror (...); exit (EXIT_FAILURE); } replace this with use of the error(3) function: if (something_bad) error (EXIT_FAILURE, errno, ...); The error(3) function is supplied by glibc, or by gnulib on platforms which don't have it, and is much more flexible than perror(3). Since we already use error(3), there seems to be

Hi Joshua, I have a function foo and I want to insert exit(0) at the end of foo. The problem is M.getFunction returns null, which is understandable. I am not sure what to do. Below is the code snippet. void foo(int argc, char* argv[]) { printf("hello world\n"); exit(0); //***I want to insert this exit } My llvm code snippet is vector<const Type *> params =

Hi, Is there currently any way to guarantee that on.exit does not fail to execute the recorded expression because of a user interrupt arriving during function exit? Consider: f <- function() { suspendInterrupts({ on.exit(suspendInterrupts(cntr_on.exit <<- cntr_on.exit + 1L)) cntr_f <<- cntr_f + 1L }) TRUE } It is possible to interrupt this function such that cntr_f