similar to: ignoring SIGPIPE signal + error loading lapack routines

Hi. I'm writing an article on network backups, and instead of using my old ssh1 software, I decided to go with openssh all the way. I got the hang of the openssh way of doing protocol 2 public key authentication, but ssh is failing to terminate when a pipe is broken. I am ssh-ing to a remote host and doing a cat or zcat of a dump file, then on the localhost, I'm using restore to extract

Hi Benjamin, you cannot pipe to echo, since it does not read from stdin. echo just echos is first arg, i.e. echo /dev/stdin > /dev/null will echo the string "/dev/stdin"to /dev/stdout, which is redirected to /dev/null. Try p <- pipe("cat > /dev/null", open = "w") instead. Regards, Andreas 2019-12-06 02:46 GMT+01:00 Benjamin Tyner<btyner at

Not sure if this is a bug, so posting here first. If I run: ?? cnt <- 0L ?? while (TRUE) { ? ? ?? cnt <- cnt + 1L ? ? ?? p <- pipe("echo /dev/stdin > /dev/null", open = "w") ? ? ?? writeLines("foobar", p) ? ? ?? tryCatch(close(p), error = function(e) { print(cnt); stop(e)}) ?? } then once cnt gets to around 650, it fails with: ?? [1] 654 ??

Andreas, How right you are! Still, I find it curious that in the context of the while(TRUE) loop, I am allowed to do this 653 times, with failure on the 654th attempt. Perhaps there is something asynchronous going on? If I eliminate the looping, it does indeed fail (as expected) on the first attempt to close the pipe. Regards Ben On 12/6/19 2:04 AM, Andreas Kersting wrote: > Hi

Hey, On 02/20/2018 11:51 PM, Paul Semel wrote: > Hello, > > > I'm Paul Semel, a French student in computer science. I am currently in > my 4th year (1st year of graduate school) at EPITA and enrolled in the > system and security laboratory of the school. > > I would be very interested in working on a LLVM project during this > GSoC. Implementing a PoC for an

Hi Eric, As you are pointed to be the confirmed mentor for the "Command line replacements for GNU Binutils" GSOC 2018 subject, I permit myself to add you to this thread ! If you have a few minutes to answer my questions, that'd really great 🙂 On 03/01/2018 08:43 PM, Paul Semel wrote: > Hey, > > On 02/20/2018 11:51 PM, Paul Semel wrote: >> Hello, >>

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.9.0 DAHDI-Tools-v2.9.0.1 dahdi-linux-complete-2.9.0+2.9.0.1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete This hotfix corrects a rare race

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.9.0 DAHDI-Tools-v2.9.0.1 dahdi-linux-complete-2.9.0+2.9.0.1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete This hotfix corrects a rare race

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.9.0-rc1 DAHDI-Tools-v2.9.0-rc1 dahdi-linux-complete-2.9.0-rc1+2.9.0-rc1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete - Introduces support

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.9.0-rc1 DAHDI-Tools-v2.9.0-rc1 dahdi-linux-complete-2.9.0-rc1+2.9.0-rc1 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete - Introduces support

Hi, Thanks for replying ! On 03/02/2018 10:58 PM, Artem Dergachev wrote: > Hey, welcome! > > I'm curious about the unsequenced modification checker, is it something > that I should have seen but missed for whatever reason? It might be > useful, and I think I'm seeing why don't compiler warnings cover all > cases, i.e. why the analyzer's path sensitivity

Hello, I'm Paul Semel, a French student in computer science. I am currently in my 4th year (1st year of graduate school) at EPITA and enrolled in the system and security laboratory of the school. I would be very interested in working on a LLVM project during this GSoC. Implementing a PoC for an unsequenced modification checker in CSA helped me discover LLVM. However, I would like to

On Fri, Aug 04, 2023 at 03:46:47PM +0300, Arseniy Krasnov wrote: >Hi Stefano, > >On 02.08.2023 10:46, Stefano Garzarella wrote: >> On Tue, Aug 01, 2023 at 05:17:26PM +0300, Arseniy Krasnov wrote: >>> POSIX requires to send SIGPIPE on write to SOCK_STREAM socket which was >>> shutdowned with SHUT_WR flag or its peer was shutdowned with SHUT_RD >>> flag.

Dear OpenSSH gurus! ;-) I recently upgraded from "OpenSSH 2.1.1p4" to "OpenSSH 2.3.0p1" on my Linux 2.2.17 box with OpenSSL 0.9.5a (RedHat 7.0). According to the "ChangeLog", there was a change in SIGPIPE handling: | 20000930 | [...] | - (djm) Ignore SIGPIPEs from serverloop to child. Fixes crashes with | very short lived X connections. Bug report from

On Fri, Aug 04, 2023 at 05:34:20PM +0300, Arseniy Krasnov wrote: > > >On 04.08.2023 17:28, Stefano Garzarella wrote: >> On Fri, Aug 04, 2023 at 03:46:47PM +0300, Arseniy Krasnov wrote: >>> Hi Stefano, >>> >>> On 02.08.2023 10:46, Stefano Garzarella wrote: >>>> On Tue, Aug 01, 2023 at 05:17:26PM +0300, Arseniy Krasnov wrote: >>>>>

On Mon, Aug 14, 2023 at 10:46:05PM +0300, Arseniy Krasnov wrote: > > >On 04.08.2023 17:28, Stefano Garzarella wrote: >> On Fri, Aug 04, 2023 at 03:46:47PM +0300, Arseniy Krasnov wrote: >>> Hi Stefano, >>> >>> On 02.08.2023 10:46, Stefano Garzarella wrote: >>>> On Tue, Aug 01, 2023 at 05:17:26PM +0300, Arseniy Krasnov wrote: >>>>>

Hello, I've got problems with Samba 3.6.0 up to 3.6.6. Forked smbd processes are closing unexpectedly and sometimes smbd server exits. (In Samba 3.5.16 everything works). When invoke smbd from gdb and turn off SIGPIPE passing (by command "handle SIGPIPE nostop nopass") everything works fine. I found out that SigBlk flag of forked smbd processes in /proc/*/status is:

While nbdkit itself must run with SIGPIPE ignored, many applications expect to inherit SIGPIPE in the default state. What's worse, POSIX states that a non-interactive shell script cannot use 'trap' to undo an inherited SIG_IGN on SIGPIPE. I have seen several bug reports over the years of something that works for a developer but fails under a CI environment, where the root cause was

appro@fy.chalmers.se wrote: > > No, it's not:-) > > static int sig_pipe(void) > { > BlockSignals( True, SIGPIPE ); > > DEBUG( 0, ("Got SIGPIPE\n") ); > if ( !is_daemon ) > exit(1); > BlockSignals( False, SIGPIPE ); > #ifndef DONT_REINSTALL_SIG >

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.9.0 DAHDI-Tools-v2.9.0 dahdi-linux-complete-2.9.0+2.9.0 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete - Introduces support for