All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: /dev/.udev/failed/devices@... problems
Date: Tue, 07 Mar 2006 16:21:51 +0000	[thread overview]
Message-ID: <20060307162151.GA7548@vrfy.org> (raw)
In-Reply-To: <aa83d1ee0602021903k6af15b1ey3302fd3f5e179c8a@mail.gmail.com>

On Tue, Mar 07, 2006 at 04:30:30PM +0100, Liontos Aristotelis wrote:
> > On 2/18/06, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > > I's unlikely. The "failed" events are created if one or more of the
> > > configured RUN= programs returns non-zero. Usually this is not a problem
> > > and can safely be ignored and seen as udev's "private" data used for
> > > coldplug.
> > > If they should go away, the rule writers must make sure, that the called
> > > tools don't return a failure or maybe should not called at all for these
> > > devices.

> The system is up and running for weeks and its stable.No error
> messages in the logs and udev with dbus and hal work as expected.
> There are still 24 devices under failed but as you said they dont
> cause any problem.(Maybe a sysfs related problem ?)

Yeah, this is not a "problem" at all, and definitely nothing sysfs
related. It is just a script called by udev which returns non-zero.
That could be "fixed" by your distro just for cosmetic reasons, but
you can also safely ignore it, if everything works fine.

Kay


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

  parent reply	other threads:[~2006-03-07 16:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  3:03 /dev/.udev/failed/devices@... problems Liontos Aristotelis
2006-02-03  3:31 ` Liontos Aristotelis
2006-02-03  4:17 ` Greg KH
2006-02-03 13:48 ` Liontos Aristotelis
2006-02-18  1:49 ` Greg KH
2006-02-18  7:01 ` Janusz Borowski
2006-02-18 21:50 ` Kay Sievers
2006-02-21 16:23 ` Liontos Aristotelis
2006-03-07 15:30 ` Liontos Aristotelis
2006-03-07 16:21 ` Kay Sievers [this message]
2006-03-07 17:16 ` Marco d'Itri
2006-03-07 17:26 ` Kay Sievers
2006-03-08  0:28 ` Liontos Aristotelis
2006-03-08  0:45 ` Marco d'Itri

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=20060307162151.GA7548@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.