http://bugzilla.novell.com/show_bug.cgi?id=585853 http://bugzilla.novell.com/show_bug.cgi?id=585853#c0 Summary: socketpair() does not generate socket pair usable as replacement as pipe Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pbaudis@novell.com ReportedBy: werner@novell.com QAContact: qa@suse.de CC: coolo@novell.com, ro@novell.com Found By: Development Blocker: --- Initial remark: the ksh uses socket pairs as replacement for pipes, also the program man. Now I found that such socket pairs do not generate a SIGPIPE where it should, e.g. from test suite of the ksh: test basic.sh begins at 2010-03-05+16:44:23 basic.sh[436]: early termination not causing broken pipe basic.sh[477]: pipefail causing /bin/true to wait for other end of pipe test basic.sh failed at 2010-03-05+16:44:51 with exit code 2 [ 95 tests 2 errors ] test signal.sh begins at 2010-03-05+16:45:50 signal.sh[55]: pipe with --pipefail PIPE trap hangs signal.sh[296]: kill -PIPE $$ failed, required termination by signal 'KILL' test signal.sh failed at 2010-03-05+16:47:06 with exit code 2 [ 26 tests 2 errors ] .. this works in SLES9, SLES10-SP3, SLES11-SP1, and SLES11, in openSUSE 11.1 and also in openSUSE 11.2. I've tried out the old gcc-4.3 compiler but this does not help therefore I guess that the glibc does generate a socket pair which does *not* rise a SIGPIPE nor a EPIPE if someone writes on a broken socket pair. As this happens within a chroot build environment it seems not to be a kernel runtime problem. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.