All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: action does not trigger on remove, only on add
Date: Tue, 28 Mar 2006 18:05:26 +0000	[thread overview]
Message-ID: <20060328180526.GA31708@vrfy.org> (raw)
In-Reply-To: <442979C9.9090908@bl.com>

On Tue, Mar 28, 2006 at 12:00:41PM -0600, Moshe Yudkowsky wrote:
> I must be missing something quite obvious.
> 
> Here are two rules:
> 
> SUBSYSTEM="block", ACTION="add", SYSFS{vendor}="iriver", 
> SYMLINK="iriver", RUN+="/etc/hotplug/usb/iriver"
> 
> SUBSYSTEM="block", ACTION="remove", SYSFS{vendor}="iriver", 
> RUN+="/etc/hotplug/usb/iriver"
> 
> The first one works quite nicely, and I can see the program in RUN 
> execute. The second rule does not run the program as far as I can tell.
> 
> I do see the "remove" event:
> 
> UDEV  [1143466033.007580] remove@/block/sdc
> UDEV_LOG=3
> ACTION=remove
> DEVPATH=/block/sdc
> SUBSYSTEM=block
> SEQNUM$91
> MINOR2
> MAJOR=8
> PHYSDEVPATH=/devices/pci0000:00/0000:00:10.3/usb4/4-4/4-4:1.0/host11/target11:0:0/11:0:0:0
> PHYSDEVBUS=scsi
> PHYSDEVDRIVER=sd
> UDEVD_EVENT=1
> DEVLINKS=/dev/iriver /dev/sdc /dev/discs/disc2/disc 
> /dev/disk/by-id/usb-iriver_MassStorage_Disc 
> /dev/disk/by-path/usb-iRiverLimited-IFP-700HIGHSPEED:0:0:0
> DEVNAME=/dev/scsi/host11/bus0/target0/lun0/disc
> ID_VENDOR=iriver
> ID_MODEL=MassStorage_Disc
> ID_REVISION\001
> ID_SERIAL=iriver_MassStorage_Disc
> ID_TYPE=disk
> ID_BUS=usb
> ID_PATH=usb-iRiverLimited-IFP-700HIGHSPEED:0:0:0
> 
> so I can't quite figure out why the program doesn't execute. This worked 
> in the past but stopped working a few releases back, and now it's 
> starting to bother me.

This never worked, cause there are no sysfs files to match against
when the device is gone.

Kay


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

  reply	other threads:[~2006-03-28 18:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 18:00 action does not trigger on remove, only on add Moshe Yudkowsky
2006-03-28 18:05 ` Kay Sievers [this message]
2006-03-28 19:08 ` Moshe Yudkowsky

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=20060328180526.GA31708@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.