similar to: [Bug 85] ssh -2 localhost od /bin/ls | true ignore SIGPIPE

http://bugzilla.mindrot.org/show_bug.cgi?id=85 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|markus at openbsd.org |openssh-unix-dev at mindrot.org Status|ASSIGNED |NEW ------- Additional Comments From markus at

http://bugzilla.mindrot.org/show_bug.cgi?id=85 ------- Comment #5 from jon at stimmel.net 2006-12-28 04:24 ------- I am running into this as well, and have not found a workaround. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=85 chris at ex-parrot.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chris at ex-parrot.com ------- Comment #4 from chris at ex-parrot.com 2006-06-22 08:50 ------- I see this bug has now been open for

Referring to "CLOSED FIXED" Bug 85: https://bugzilla.mindrot.org/show_bug.cgi?id=85 Assuming that you have your machine setup so that the following commands run without prompting: ssh -2 localhost pwd ssh -1 localhost pwd Then this command: ssh -1 localhost yes | true always produces this output: Write failed flushing stdout buffer. write stdout: Broken pipe Yet

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

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 ??

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

(I am not on the rsync mailing list, so if you send a response to this message to the list, please be sure to CC me.) I first reported this bug go Red Hat in <URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65350>. If you run rsync with a subshell through ssh.com's ssh and sshd and then kill the client with ctrl-C, the rsync server process running on the remote machine grows

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

Hello, I have several systems which I recently updated with yum -y update to all the latest packages. These systems use yum-priorities and use the CentOS (priority 1) EPEL (priority 5) and rpmforge (priority 10) repositories. After the updates, dhcpd stopped working with a SIGPIPE error which occurs shortly after it attempts to fork into the background. I worked around that problem by building

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:

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

Hi R-devel, tcltk devel, and sqldf devel, The transcript below shows how loading the tcl/tk library in under R causes subprocesses to ignore SIGPIPE. I am including the developer of the (wonderful) sqldf package since it requires tcltk and you might like to make this dependence optional to the user (at least until this is fixed in tcltk). Am I mistaken in calling this a 'bug'? Any

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -------------- next part -------------- >From 6b1f24fb3bf4427ec2115278ee163e05b645cfee Mon Sep 17

Dear list I don't know whether this is the right place to post this message. If not, please redirect me to the proper place. i have a Perl application on Linux that uses R (V2.9.0) through the Perl-R interface. basically, the application performs statistical analysis using R, and displays the R output (JPG image of the particular analysis) to the user. in general, this works fine. but i

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

I am running OpenSSH 2.9p1 on SunOS 5.7 w/4-24-2001 patch cluster. Like many other users I am seeing the hanging session on logout with background processes. This is a huge problem for me as I centrally manage 50+ machines with rdist across ssh. Instead of just complaining about the problem I thought I would put my CS degree to use and try to track down the problem myself. For starters,

The command "ssh ls -l /doesnotexist" gives various responses: Running from a 200 MHz PentiumPro with dsa key added to ssh-agent: Mistakes worst to fast machine: To a faster 600 MHz dual processor i686 600 MHz machine: ls: /doesnotexist: No such file or directory -- correct nothing at all -- wrong ls: select: Bad file descriptor -- wrong

The 4.6p1 sshd is logging this error during remote commands or file transfers: error: channel 0: chan_read_failed for istate 3 Platform is Solaris 8, 4.6p1 + OpenSSL 0.9.8d. The commands and transfers work correctly, so the error message appears to be spurious. The error message does not appear when processing logins. Otherwise 4.6p1 is running without any apparent problems. This error

The short version: There's a "#define USE_PIPES" in the middle of session.c; it would be better if it were in (e.g.) defines.h or some other .h file. (If in fact it needs to be defined at all; I'm not convinced that it does.) Here's the (much) longer version: I recently installed the latest OpenSSH on some of our servers (RHEL5, which provides the 4.3 release) and soon