From owner-freebsd-hackers Mon Sep 23 6:35:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3110737B401 for ; Mon, 23 Sep 2002 06:35:27 -0700 (PDT) Received: from star.rila.bg (star.rila.bg [62.73.64.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6401543E65 for ; Mon, 23 Sep 2002 06:35:23 -0700 (PDT) (envelope-from vladimirt@rila.bg) Received: from star.rila.bg (vlady@localhost [127.0.0.1]) by star.rila.bg (8.12.5/8.12.5) with SMTP id g8NDYIYZ089211 for ; Mon, 23 Sep 2002 16:35:03 +0300 (EEST) (envelope-from vladimirt@rila.bg) Date: Mon, 23 Sep 2002 16:34:18 +0300 From: Vladimir Terziev To: hackers@FreeBSD.ORG Subject: Problems catching SIGPIPE when writing to a broken stream Message-Id: <20020923163418.216b14ae.vladimirt@rila.bg> X-Mailer: Sylpheed version 0.8.2 (GTK+ 1.2.10; i386-unknown-freebsd4.6) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi hackers, I'm implementing a programmme, which writes a big amount of data (using write(2)) to a socket. When the communication stream has been closed by some reason, during the write(2) call, my process receives SIGPIPE. I tryed to catch it with signal(3) and change the behaviour of write(2) call with siginterrupt(3), but SIGPIPE is still raised to my process and terminates it. Any help and ideas will be useful! regards, Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message