From: Michael Buesch <mbuesch@freenet.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev zombies
Date: Sun, 06 Jun 2004 10:08:09 +0000 [thread overview]
Message-ID: <200406061208.10208.mbuesch@freenet.de> (raw)
In-Reply-To: <200406011914.13245.mbuesch@freenet.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
So I applied this patch to udevd:
- --- udev.official/udevd.c 2004-05-30 10:57:03.000000000 +0200
+++ udev.m/udevd.c 2004-06-05 16:03:31.000000000 +0200
@@ -325,7 +325,7 @@
goto do_write;
break;
default:
- - dbg("unhandled signal");
+ dbg("unhandled signal %d", signum);
return;
}
Result in my syslog is:
Jun 6 11:32:21 lfs kernel: udevd[329]: sig_handler: unhandled signal -4
Heh? Somebody out there who could interpret it?
Some time ago I wrote the sig_handler() myself and I submitted a patch to
Greg. It was absolutely impossible to trigger "default:" IMHO and it still
should be. (There were some changes, but I can't find why it's triggered)
And my zombie problem is still there. :)
And again: I'm using klibc. With glibc everything seems to work fine.
(haven't checked the sig_handler() stuff, but at least there are no
zombies)
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAwu0JFGK1OIvVOP4RAk1EAJ49mgLjv/6oUDUfuLnq/KzV/PnPnACgw1f3
6DgQkumszxW8yCllaiTDTwk=0i/c
-----END PGP SIGNATURE-----
-------------------------------------------------------
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-06 10:08 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
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 [this message]
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=200406061208.10208.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--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 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 NNTP newsgroup(s).