From: "Sue Alfano" <smalfano@gmail.com>
To: linux-kernel@vger.kernel.org, "James Chapman" <jchapman@katalix.com>
Subject: Re: uClibc - waitid()
Date: Thu, 25 Jan 2007 14:47:15 -0500 [thread overview]
Message-ID: <fb6b09f20701251147n76388866tb66a825a5f1041c@mail.gmail.com> (raw)
In-Reply-To: <45AFE875.5040204@katalix.com>
Well, I'm back. I didn't get any help from the uClibc folks, but I eventually
figured out how to get to the waitid function in the kernel using the _syscall4
macro and the right header file. waitid worked great, but then I started
having problems when more than one child needed to be reaped.
Basically, the parent process registers a SIGCHLD signal handler via sigaction()
with the SA_RESTART option and then sits on a timed select(). All the signal
handler does is set a flag - the waitid processing takes place when the parent
drops out of the select because of the signal or a timeout. When the waitid
succeeds, the pid is used to do some processing and then is used to call
waitpid to clean up the mess. This is all in a while loop, so when the waitid
is called again, 0 is returned with si_pid = 0 indicating that there are no
more children to reap. That's all great. The problem occurs when there's 2
or more children to reap. When this occurs, the 2nd waitid call returns -1
and si_pid = 0. The waitid continues to fail in this manner until the parent
receives another SIGCHLD signal, then it works for the next zombie child in
the waiting line, but only one. I can send SIGCHLD kills to the parent from
the console and eventually get everything cleaned up. Sending the kill from
the parent isn't enough - I suppose it wants to be blocking on the select.
I tried registering the signal handler without SA_RESRART and also via signal(),
since there was a posting about SA_RESTART, but that made no difference. I
also tried not having a signal handler at all, but then I couldn't reap any
children on the timeout.
So, are there known issues with waitid when there are multiple children piled
up waiting to be reaped? If so, is there a patch or a workaround?
The product that I'm working on is using Linux version 2.6.12-2.0.0-258
Thanks for any help,
Sue
On 1/18/07, James Chapman <jchapman@katalix.com> wrote:
> You're asking the wrong list. Try the uClibc list at uclibc.org.
>
> glibc and uClibc provide C APIs to kernel system calls. uClibc doesn't
> implement all features that glibc supports - there are several kernel
> APIs that uClibc doesn't expose. Ask the uClibc folk for advice.
>
> --
> James Chapman
> Katalix Systems Ltd
> http://www.katalix.com
> Catalysts for your Embedded Linux software development
>
prev parent reply other threads:[~2007-01-25 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 11:18 Sue Alfano
2007-01-18 21:36 ` James Chapman
2007-01-25 19:47 ` Sue Alfano [this message]
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=fb6b09f20701251147n76388866tb66a825a5f1041c@mail.gmail.com \
--to=smalfano@gmail.com \
--cc=jchapman@katalix.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®