From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev zombies
Date: Fri, 04 Jun 2004 08:03:50 +0000 [thread overview]
Message-ID: <20040604080350.GA10482@vrfy.org> (raw)
In-Reply-To: <200406011914.13245.mbuesch@freenet.de>
On Thu, Jun 03, 2004 at 08:45:31PM -0500, jnf wrote:
> looking through udevd.c right now at the signal handling routines, I see
> that sig_handler is the routine called by all of the custom signal
> handlers and it is just a switch statement and tests for SIGINT, SIGTERM
> SIGALRM and SIGCHLD, so in theory [obviously nothing works as it should in
> theory], we should never see the default statement, which is what we are
> seeing- I havent had much of a chance to look at it, but i noticied this
> line:
> act.sa_andler = sig_handler;
>
> is that a typo, or is there something I'm not understanding? Shouldn't
> that be act.sa_handler? I just changed the dbg() statement from unhandled
> signal to dbg("unhandled signal number #\n", signum);, so im going to
> reboot in a moment and then try to cause it to recieve the signal, also
> its my gf's birthday so I won't have much more time tonight to play.
Come on, how can you compile this? I can't find this "typo" in the code.
thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-06-04 8:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 17:14 udev zombies Michael Buesch
2004-06-02 16:53 ` Greg KH
2004-06-02 18:26 ` Michael Buesch
2004-06-03 8:24 ` Harald Hoyer
2004-06-03 8:27 ` Harald Hoyer
2004-06-03 8:54 ` jnf
2004-06-04 1:45 ` jnf
2004-06-04 8:03 ` Kay Sievers [this message]
2004-06-04 8:36 ` jnf
2004-06-04 8:39 ` jnf
2004-06-04 9:32 ` Kay Sievers
2004-06-04 17:23 ` jnf
2004-06-06 10:08 ` Michael Buesch
2004-06-06 10:52 ` Kay Sievers
2004-06-06 11:16 ` Michael Buesch
2004-06-06 13:16 ` Kay Sievers
2004-06-06 13:38 ` Michael Buesch
2004-06-06 23:37 ` Kay Sievers
2004-06-07 2:20 ` Greg KH
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=20040604080350.GA10482@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.