Date: Fri, 9 Jul 2004 12:42:36 -0400 (EDT) From: Matthew George <mdg@secureworks.net> To: freebsd-hackers@freebsd.org Subject: SIGURG (fwd) Message-ID: <20040709123123.T2363@localhost>
next in thread | raw e-mail | index | archive | help
[ no response from questions@ =\ ] <original message> 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 ... </original message> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040709123123.T2363>