From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev too slow?
Date: Sun, 28 Aug 2005 23:28:35 +0000 [thread overview]
Message-ID: <20050828232835.GA3920@vrfy.org> (raw)
In-Reply-To: <8F1EED683FFEDD43B4FE4A0425847F2EAEE581@EXE.ceda.polimi.it>
On Sat, Aug 20, 2005 at 08:16:44PM +0200, Uberto Barbini wrote:
> > > UEVENT[1124474095] add@/class/dvb/dvb0.frontend0
> > > UDEV [1124474099] add@/class/dvb/dvb0.frontend0
> >
> > Looks like something that can be fixed. :)
> >
> > Please send me the 'dvb.debug' file written with:
> > DEVPATH=/class/dvb/dvb0.frontend0 ACTIONd strace -o dvb.debug -s1000
> > -p -f /sbin/udev dvb
>
> Ok, the -p option is not accepted so I removed it. I'm not sure but I launched
> with dvb modules loaded.
>
> Here it cames:
>
> 9973 execve("/sbin/udev", ["/sbin/udev", "dvb"], [/* 38 vars */]) = 0
It is a bug in the daemon. This hopefully fixes and explains it:
http://ehlo.org/~kay/?p=linux/hotplug/udev-kay.git;a=commitdiff;hi348b66ff4163a2fbf974bde649e5bc963462b4
Thanks,
Kay
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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
prev parent reply other threads:[~2005-08-28 23:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 10:10 udev too slow? Barbini Uberto
2005-08-19 11:41 ` Kay Sievers
2005-08-19 19:54 ` Uberto Barbini
2005-08-19 20:36 ` Kay Sievers
2005-08-19 22:56 ` Greg KH
2005-08-20 18:16 ` Uberto Barbini
2005-08-20 19:11 ` Kay Sievers
2005-08-28 23:28 ` Kay Sievers [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=20050828232835.GA3920@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.