From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug and test and set
Date: Sun, 02 Jan 2005 01:27:10 +0000 [thread overview]
Message-ID: <20050102012710.GA23079@wonderland.linux.it> (raw)
In-Reply-To: <200501020003.46376.rdorsch@web.de>
On Jan 02, Rainer Dorsch <rdorsch@web.de> wrote:
> My problem is that this script is called four times when the dongle is plugged
> in. I order to avoid to call pand four times, I added a poor test and set to
> the script to add a lock when a pand is running. Does anybody know, what I
> could do to get a better locking behaviour, e.g. an atomic test and set?
From http://linux-hotplug.sourceforge.net/?selected=usb:
There are two kinds of usb hotplug event: device, and interface. Kernel
2.6 added device events, as well as reporting the complete set of
interface events. You can tell which kind of event by the environment
variables: device events don't include PRODUCT, or any of the other
parameters here except DEVPATH and ACTION.
So:
# ignore device events
[ "$PRODUCT" ] || exit 0
--
ciao,
Marco
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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
next prev parent reply other threads:[~2005-01-02 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 23:03 hotplug and test and set Rainer Dorsch
2005-01-02 0:06 ` Kay Sievers
2005-01-02 1:27 ` Marco d'Itri [this message]
2005-01-02 13:30 ` Rainer Dorsch
2005-01-02 15:23 ` Kay Sievers
2005-01-02 17:07 ` Rainer Dorsch
2005-01-02 18:15 ` Kay Sievers
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=20050102012710.GA23079@wonderland.linux.it \
--to=md@linux.it \
--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).