From: "Karl O. Pinc" <kop@meme.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: WAIT_FOR_SYSFS error, Is my udev rule wrong?
Date: Thu, 20 Nov 2008 14:37:21 +0000 [thread overview]
Message-ID: <1227191841l.12277l.0l@mofo> (raw)
In-Reply-To: <1227160064l.14872l.4l@mofo>
On 11/20/2008 12:30:19 AM, Kay Sievers wrote:
> On Thu, Nov 20, 2008 at 06:47, Karl O. Pinc <kop@meme.com> wrote:
> > I've written a udev rule and am looking
> > for comment by those with more experience
> > to see if there are improvements to be made.
> > KERNEL="ttyUSB0", ACTION="add", WAIT_FOR_SYSFS="subsystem/ttyUSB0"
>
> The device you get the event for has only a single attribute, called
> "dev" and there is never a need to wait for that. WAIT_FOR* is to work
> around (in most cases broken and should be fixed) sysfs timing issues
> in the kernel. Seems, there is nothing in your event where that would
> be needed.
>
> What are you trying to wait for?
I am trying to wait long enough that at startup the ldc4linux
daemon does not log the error:
Nov 19 16:15:00 mustard LCD4Linux[15799]: Pertelian: open(/dev/ttyUSB0)
failed: No such file or directory
It seems to work anyway, but I interpret the error to mean that
something in udev has not finished by the time the daemon
starts. I don't get the error if I start lcd4linux
manually after plugging in the lcd panel.
Thanks for the help.
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
next prev parent reply other threads:[~2008-11-20 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 5:47 WAIT_FOR_SYSFS error, Is my udev rule wrong? Karl O. Pinc
2008-11-20 6:30 ` Kay Sievers
2008-11-20 14:37 ` Karl O. Pinc [this message]
2008-11-20 14:49 ` Kay Sievers
2008-11-20 15:41 ` Karl O. Pinc
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=1227191841l.12277l.0l@mofo \
--to=kop@meme.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).