From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev PROGRAM action
Date: Wed, 24 Aug 2005 09:05:01 +0000 [thread overview]
Message-ID: <20050824090501.GB5122@vrfy.org> (raw)
In-Reply-To: <430C262A.6020103@xtra.co.nz>
On Wed, Aug 24, 2005 at 07:47:54PM +1200, Miles Roper wrote:
> Hi,
>
> I've been trolling around the net trying to find an answer to why I can't
> get udev to correctly run a remove event in a script.
>
> here is my udev line
>
> BUS="usb", KERNEL="sd*", NAME="%k", PROGRAM="/etc/udev/scripts/usb.sh %k"
>
> this works fine. it calls the script below...
...
> the add event works great. however, the remove event never gets actioned.
> In fact the script never gets run when the device is removed. any ideas
> why?
PROGRAM is for evaluation of the device name. It is called before the
device node is created. If you have NAME in a rule, the rule will never
be called for any ather action than "add". Just remove "NAME="%k".
And better use RUN, it is called after device node handling.
Kay
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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-08-24 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 7:47 udev PROGRAM action Miles Roper
2005-08-24 9:05 ` Kay Sievers [this message]
2005-08-24 9:27 ` Thierry Vignaud
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=20050824090501.GB5122@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.