From: Petr Lautrbach <plautrba@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udevadm monitor --filter= with GL_PLAIN comparison
Date: Thu, 19 Mar 2009 09:38:14 +0000 [thread overview]
Message-ID: <49C21286.2070501@redhat.com> (raw)
In-Reply-To: <1237404881-1342-1-git-send-email-plautrba@redhat.com>
Kay Sievers wrote:
> On Wed, Mar 18, 2009 at 20:34, Petr Lautrbach <plautrba@redhat.com> wrote:
>> My idea is to allow user to specify simple filters for monitoring udev events.
>>
>> Events are printed only if pass all of filters.
>>
>> There is only GL_PLAIN comparison now.
>>
>> e.g.:
>> $ udevadm monitor --filter='SUBSYSTEM="bluetooth"' --filter='ACTION!="add"'
>>
>> This command prints only events which match "bluetooth" SUBSYSTEM and ACTION other
>> than "add".
>>
>> I'll be glad to hear your opinions
>
> Funny. What are you using the monitor for, that you want to filter on
> events? It's a pure debugging tool, and you usually need to see all
> events in the sequence, like the parent devices coming and going.
>
One of goal of Fedora Powermanagement feature is framework that will allow services to start
depending on installed hardware or software and I'm using this filter to monitor only
events which are defined in my udev rules e.g. for bluetooth see [1].
At first, I was writing rules with RUN+="socket:..." and perl script waiting for events on socket but
this way is looks better for me and it's usable without need any other socket or script.
[1] https://bugzilla.redhat.com/show_bug.cgi?idH4345#c12
Regards,
Petr
--
Petr Lautrbach, Red Hat, Inc.
prev parent reply other threads:[~2009-03-19 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 19:34 [PATCH] udevadm monitor --filter= with GL_PLAIN comparison Petr Lautrbach
2009-03-19 1:33 ` Kay Sievers
2009-03-19 9:38 ` Petr Lautrbach [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=49C21286.2070501@redhat.com \
--to=plautrba@redhat.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).