Re: Why not picking up ENV variables?

[Moshe Yudkowsky <msha5_17@bl.com>]

In another test, I've modified the rules:

SUBSYSTEM="block" IMPORT{program}="path_id $devpath"

SUBSYSTEM="block", ACTION="add", ENV{ID_VENDOR}="iriver", 
ENV{ID_SERIAL}="iriver_MassStorage_Disc", SYMLINK+="iriver", 
RUN+="/etc/hotplug/usb/iriver", ENV{REMOVE_CMD}="/etc/hotplug/usb/iriver 
remove"

SUBSYSTEM="block", ACTION="remove",  ENV{ID_VENDOR}="iriver", 
ENV{ID_SERIAL}="iriver_MassStorage_Disc", RUN+="/etc/hotplug/usb/iriver 
remove"

and I've also set them to run *after* the persistent.rules file. This 
should make certain that ID_VENDOR and ID_PATH are in the ENV -- even 
though I've certainly seen them in udevinfo printouts even without 
adding path_id myself.

While "add" works, the "remove" does not work. Furthermore, even thought 
run.rules executes, the ENV{REMOVE_CMD} that I've set does not run.

Help?

-- 
  Moshe Yudkowsky
  work: http://www.Disaggregate.com
  book: http://www.PebbleAndAvalanche.com


-------------------------------------------------------
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