From: Michael Buesch <mbuesch@freenet.de>
To: linux-hotplug@vger.kernel.org
Subject: udev zombies
Date: Tue, 01 Jun 2004 17:14:11 +0000 [thread overview]
Message-ID: <200406011914.13245.mbuesch@freenet.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
mb@lfs:~> ps aux|grep udev
root 345 0.0 0.0 80 56 ? S< 08:16 0:00 udevd
root 1604 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1605 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1606 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1607 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1608 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1609 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1610 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1611 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1612 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1613 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1614 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1632 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1633 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1634 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1635 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1636 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1637 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1638 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1639 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1640 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1641 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1642 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1643 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1644 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
root 1645 0.0 0.0 0 0 ? Z< 08:16 0:00 [udev] <defunct>
I expect all these zombies shouldn't be there 8-)
I am using bk as of 30.June.
Kernel is 2.6.7-rc2-bk1.
udev compile flags: USE_LOG˙lse DEBUG˙lse USE_KLIBC=true
Any idea?
Please CC me, as I'm not subscribed.
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAvLljFGK1OIvVOP4RAu8OAJ9NofGlZ/6g+iPuyVYJiObibijQHQCgkOAa
+kwzPVswKxrmEfTI39IHq24=SNsw
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
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 reply other threads:[~2004-06-01 17:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 17:14 Michael Buesch [this message]
2004-06-02 16:53 ` udev zombies 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
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=200406011914.13245.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 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.