From: Kevin Buettner <kevinb@redhat.com>
To: rda@sources.redhat.com
Subject: [PATCH] Ignore thread related realtime signals
Date: Thu, 03 Jun 2004 18:35:00 -0000 [thread overview]
Message-ID: <20040603113459.5e48889c@saguaro> (raw)
My previous patch on this matter worked for uClibc, but not for glibc.
The patch below makes it work for both.
* server.c (main): Ensure that thread related realtime signals
are ignored.
Index: server.c
===================================================================
RCS file: /cvs/src/src/rda/unix/server.c,v
retrieving revision 1.5
diff -u -p -r1.5 server.c
--- server.c 20 Apr 2004 20:08:52 -0000 1.5
+++ server.c 3 Jun 2004 18:25:32 -0000
@@ -374,6 +374,7 @@ main (int argc, char **argv)
signal (SIGCHLD, chld_handler);
+#if defined(__SIGRTMIN) && defined(__SIGRTMAX)
{
int sig;
/* Ignore realtime signals. We do this so as to not terminate
@@ -381,9 +382,10 @@ main (int argc, char **argv)
realtime signals are used for thread support, and, for some
reason, some environments send these signals to RDA as well
as the application. (And some don't.) */
- for (sig = SIGRTMIN; sig <= SIGRTMAX; sig++)
+ for (sig = __SIGRTMIN; sig <= __SIGRTMAX; sig++)
signal (sig, SIG_IGN);
}
+#endif
if (portno != 0)
{
reply other threads:[~2004-06-03 18:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040603113459.5e48889c@saguaro \
--to=kevinb@redhat.com \
--cc=rda@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).