From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 9 16:42:38 2004 Return-Path: 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 927B016A4CE for ; Fri, 9 Jul 2004 16:42:38 +0000 (GMT) Received: from mail.secureworks.net (mail.secureworks.net [209.101.212.155]) by mx1.FreeBSD.org (Postfix) with SMTP id F11DE43D5A for ; Fri, 9 Jul 2004 16:42:37 +0000 (GMT) (envelope-from mdg@secureworks.net) Received: (qmail 2065 invoked from network); 9 Jul 2004 16:42:27 -0000 Received: from unknown (HELO HOST-192-168-8-243.internal.secureworks.net) (63.239.86.253) by mail.secureworks.net with SMTP; 9 Jul 2004 16:42:27 -0000 Date: Fri, 9 Jul 2004 12:42:36 -0400 (EDT) From: Matthew George X-X-Sender: mdg@localhost To: freebsd-hackers@freebsd.org Message-ID: <20040709123123.T2363@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: SIGURG (fwd) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2004 16:42:38 -0000 [ no response from questions@ =\ ] I have a fairly active program that forks and uses pipes to communicate back to the parent before exiting. When I go to wait() on the child, occasionally the status is signaled - SIGURG instead of exit()ing normally. It appears the child process is doing everything it needs to be doing. What will generate this signal? Is it safe to ignore, or should I be handling it somehow? This is running on 4.10 ... As an update, I went ahead and masked the signal. When I did this, my 15 min load, usually at about 6 or so when this is running, dropped to approx 1.5 and has been there for a week now (is this expected/normal?). The application works as it should, but I'm still curious as to the origin of the signal, what condition it is indicating, and what the Right Thing (tm) to do is when one gets delivered. I haven't found any particularly enlightening documentation in my search so far ... any references would be most welcome ... -- Matthew George SecureWorks Technical Operations