From: Keith Pine <kpine@ddn.com>
To: linux-hotplug@vger.kernel.org
Subject: device properties and change events
Date: Wed, 27 Mar 2013 04:47:39 +0000 [thread overview]
Message-ID: <F391FB4F21BEC943926789308B8035905C5C8FD8@LAX-EX-MB3.datadirect.datadirectnet.com> (raw)
I'm using udev-147 in CentOS 6.3.
I have two rules that import properties into the udev db. I'll use a
simplified example.
IMPORT{program}="program1 %k"
ACTION="add", IMPORT{program}="program2 %N"
program1 exports MY_FOO, and program2 exports MY_BAR. I've noticed that
when a change event is triggered, MY_BAR is no longer available in the
udev database. So it appears change events clear the existing environment.
The work done in program2 is relatively expensive so I'd rather only run
it when the device is first added.
It looks like I can re-import MY_BAR if I use IMPORT{db} in a separate
rule:
IMPORT{program}="program1 %k"
ACTION="add", IMPORT{program}="program2 %N"
ACTION="change", IMPORT{db}="MY_BAR"
Is this the correct approach? Or is there another way to persist the
properties that were imported during add, besides re-importing program2?
Also, is it possible to determine *what* causes a change event to occur?
With 'udevadm monitor' I can see change events being triggered whenever my
application exits (for the devices it has opened), and would like to
determine why. I was hoping udev could give me a hint.
-Keith
next reply other threads:[~2013-03-27 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 4:47 Keith Pine [this message]
2013-03-28 22:58 ` device properties and change events Greg KH
2013-03-29 1:26 ` Keith Pine
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=F391FB4F21BEC943926789308B8035905C5C8FD8@LAX-EX-MB3.datadirect.datadirectnet.com \
--to=kpine@ddn.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 read-only IMAP folder(s) and NNTP newsgroup(s).