From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev zombies
Date: Wed, 02 Jun 2004 16:53:02 +0000 [thread overview]
Message-ID: <20040602165302.GE7829@kroah.com> (raw)
In-Reply-To: <200406011914.13245.mbuesch@freenet.de>
On Tue, Jun 01, 2004 at 07:14:11PM +0200, Michael Buesch wrote:
> 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 would expect them not to be there too :)
Care to rebuild udev with
make USE_LOG=true DEBUG=true
and let us know what the syslog messages are for those dead udev
instances?
thanks,
greg k-h
-------------------------------------------------------
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-02 16:53 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 [this message]
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=20040602165302.GE7829@kroah.com \
--to=greg@kroah.com \
--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).