search for: sigint

All, When logging into an HP-UX 10.2 system from a Windows NT machine running Cygwin and openssh 2.9p2, control-c sends a sigint to the ssh client on the NT system, thus killing the ssh process. Interestingly enough, this behavior is only observed when using X11 forwarding. I can eliminate the behavior by changing clientloop.c to ignore SIGINT (signal(SIGINT, SIG_IGN) ) but then I'm bak to the old behavior of the remot...

Hi All, I realize that this is not a really nice reprex, but anyone has an idea why a background R session would "remember" an interrupt (SIGINT) on Unix? rs <- callr::r_session$new() rs$interrupt() # just sends a SIGINT #> [1] TRUE rs$run(function() 1+1) #> Error: interrupt rs$run(function() 1+1) #> [1] 2 It seems that the main loop somehow stores the SIGINT it receives while it is waiting on stdin, and then it triggers...

Yeah, I get that they are async. What happens is that the background process is not doing anything when the process gets a SIGINT. I.e. the background process is just listening on its standard input. AFAICT for an interactive process such a SIGINT is just swallowed, with a newline outputted to the terminal. But apparently, for this background process, it is not swallowed, and it is triggered later. FWIW it does not happen o...

Hi, I was wondering if anybody knew how to trap SIGINTs (ie Ctrl-C) in backend C++ code for R extensions? I'm writing a package that uses the GPU for some hefty matrix operations in a tightly coupled parallel algorithm implemented in CUDA. The problem is that once running, the C++ module cannot apparently be interrupted by a SIGINT, leaving the u...

..., I managed to create an example without callr, but it is still somewhat cumbersome. Anyway, here it is. Terminal 1: mkfifo fif R --no-readline --slave --no-save --no-restore < fif Terminal 2: cat > fif Sys.getpid() This will make Terminal 1 print the pid of the R process, so we can send a SIGINT: Terminal 3: kill -INT pid The R process is of course still running happily. Terminal 2 again: tryCatch(Sys.sleep(10), interrupt = function(e) e) and then Terminal 1 prints the interrupt condition: <interrupt: > This is macOS and 3.5.3, although I don't think it matters much. Thanks...

Unfortunately --interactive also makes the session interactive(), which is bad for me, as it is a background session. In general, I don't want the interactive behavior, but was wondering if I could send as SIGINT to try to interrupt the computation of the background process, and if that does not work, then I would send a SIGKILL and start up another process. It all works nicely, except for this glitch, but I think I can work around it. Thanks, Gabor On Tue, Apr 30, 2019 at 10:55 PM Tierney, Luke <luke-...

...Most of the WIN32 processing is event-based. Cheers, Simon > On Apr 30, 2019, at 4:17 PM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > > Yeah, I get that they are async. > > What happens is that the background process is not doing anything when > the process gets a SIGINT. I.e. the background process is just > listening on its standard input. > > AFAICT for an interactive process such a SIGINT is just swallowed, > with a newline outputted to the terminal. > > But apparently, for this background process, it is not swallowed, and > it is trigger...

...still > somewhat cumbersome. Anyway, here it is. > > Terminal 1: > mkfifo fif > R --no-readline --slave --no-save --no-restore < fif > > Terminal 2: > cat > fif > Sys.getpid() > > This will make Terminal 1 print the pid of the R process, so we can > send a SIGINT: > > Terminal 3: > kill -INT pid > > The R process is of course still running happily. > > Terminal 2 again: > tryCatch(Sys.sleep(10), interrupt = function(e) e) > > and then Terminal 1 prints the interrupt condition: > <interrupt: > > > This is macOS an...

...-03-16-210209" failed: Operation not permitted (1) rsync: recv_generator: mkdir "/Volumes/G-DRIVE Thunderbolt 3/Backups.backupdb/André Althoffs iMac/2016-04-11-130912" failed: Operation not permitted (1) *** Skipping any contents from this failed directory *** ^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(700) [sender=3.1.3] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504) [generator=3.1.3] iMac:~ andre$ mount /dev/disk0s2 on / (hfs, local, journaled) devfs on /dev (devfs, local, nobrowse) map -hosts on /net (autofs, nosuid, automounted...

...it.) This is a pretty regular occurance for me, and some others I've talked to - usually when you realize that the scp command you typed has a typo and decide to abort. Strangely, ssh handles this correctly, but scp does not. The single handler in scp.c is killchild(), which should pass the SIGINT along to the ssh process, which would restore the terminal. However this doesn't work for some reason I couldn't discern - perhaps the ssh process is invoked in such a way that it doesn't have access to the terminal settings? I created the attached patch which fixes the problem by sav...

...PM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > > Unfortunately --interactive also makes the session interactive(), > which is bad for me, as it is a background session. > > In general, I don't want the interactive behavior, but was wondering > if I could send as SIGINT to try to interrupt the computation of the > background process, and if that does not work, then I would send a > SIGKILL and start up another process. It all works nicely, except for > this glitch, but I think I can work around it. > > Thanks, > Gabor > > On Tue, Apr 30,...

https://bugzilla.samba.org/show_bug.cgi?id=9502 Summary: Deamon deadlock at stop (SIGINT caught) Product: rsync Version: 3.0.7 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: jurij at ocslab.com Q...

# HG changeset patch # User inakoshi.hiroya@jp.fujitsu.com # Date 1191287395 -28800 # Node ID 5543e74774a826b1781893982ed5052312b820fc # Parent 83239b2890723e0c06bad507bb273a970784b18e Flush stdout when xentop -b gets SIGINT and SIGTERM. It is useful when you stop xentop -b by keyboard interrupt or by other programs such as killall from a batch script. You would have missed the bottom part of xentop outputs without this patch. Signed-off-by: INAKOSHI Hiroya <inakoshi.hiroya@jp.fujitsu.com> diff -r 83239b289072...

...xit" c. "sh -c '.../bin/true; exit'" The results for the architectures I was able to test are: 2.0.4 2.0.5 -------------------------------------------------------------------- alpha/alpha-linux-gnu: fail: fcntl, sigint, 2c fail: sigint, 2c arm/arm-linux-gnueabi: pass pass arm/arm-linux-gnueabihf: pass pass arm64/aarch64-linux-gnu: fail: fcntl pass i386/i686-linux-gnu: fail: build pass m68k/m68k-linux-gnu:...

...uot; failed: Operation not permitted (1) > rsync: recv_generator: mkdir "/Volumes/G-DRIVE Thunderbolt 3/Backups.backupdb/André Althoffs iMac/2016-04-11-130912" failed: Operation not permitted (1) > *** Skipping any contents from this failed directory *** > ^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(700) [sender=3.1.3] > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504) [generator=3.1.3] > iMac:~ andre$ mount > /dev/disk0s2 on / (hfs, local, journaled) > devfs on /dev (devfs, local, nobrowse) > map -hosts on /net (au...

...in real time with the possibility of significant lag between events. When processing an event, I can make use of R_CheckUserInterrupt, but while the external library code is waiting on a new event, I don't have an opportunity to call this - my entry points are only on events. I can capture a SIGINT by redefining signal(SIGINT, myhandler) before calling the lib, but I am somewhat at a loss in terms of what I can do within the handler that would let me pass control back to R. void myhandler (int s) { error("interrupt caught!"); } Works, but I am sure it isn't supposed to. In...

...ssue. Please let me know if you need more information. ============= Start of rsync Block @ Wed Dec 23 10:25:43 SGT 2009 ================ Wed Dec 23 10:25:43 SGT 2009 copying/updating/deleting /svcm/u02/rsync/cron_rsyncexecute_prod.sh building file list ... rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(231) Rsync failure to rsync://oMy2portalProdRsync at lnx09:9060/oMy2Lnx09Prod - Error Code: 20. Error Desc: Received SIGUSR1 or SIGINT Subject:Rsync failure to rsync://oMy2portalProdRsync at lnx09:9060/oMy2Lnx09Prod - Error Code: 20. Error Desc: Received SIGUSR1 or SIGINT Rsy...

...is to "keep partially transferred files". I'm assuming if I don't have partial flag any partially transferred files should be deleted. However this is not what I'm seeing. Example: (Using a big file so that rsync times a while to run. This gives me time to hit CTRL-C for the SIGINT). > mkdir example > dd if=/dev/zero of=example/big_file bs=1024 count=102400 > ls -l example -rw-r--r-- 1 jmitchell users 104857600 2006-05-18 16:33 big_file > rsync -ptgou example/big_file . # Let it run for a couple of seconds to start running, then hit CTRL-C rsync error: receive...

...he next evaluation. Cheers, Simon > On Apr 30, 2019, at 3:44 PM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > > Hi All, > > I realize that this is not a really nice reprex, but anyone has an > idea why a background R session would "remember" an interrupt (SIGINT) > on Unix? > > rs <- callr::r_session$new() > rs$interrupt() # just sends a SIGINT > #> [1] TRUE > > rs$run(function() 1+1) > #> Error: interrupt > > rs$run(function() 1+1) > #> [1] 2 > > It seems that the main loop somehow stores the SIGI...

How would you spec out a call to Signal.trap (a ^C or a unix SIGINT)? Scott