It'll cause your script to be run for each device that has
IS_ONETOUCH=yes.
If you have multiple onetouch devices, you'll have multiple copies of
your script run.
--
udev calls my script for "add" but not for "remove"
https://bugs.launchpad.net/bugs/135429
You received this bug notification beca
Thanks for the clarification! What if the disk is inserted and thus the
env var is set, then another device is removed? Will that cause my
script (handle-onetouch.sh) to be executed?
--
udev calls my script for "add" but not for "remove"
https://bugs.launchpad.net/bugs/135429
You received this bu
Ah, sorry, this envvar isn't supported in 6.06 - in fact, := probably
isn't either.
The alternate is to set your own variable, ie;
BUS=="usb", KERNEL=="sd?", SYSFS{product}=="Maxtor OneTouch III",
ENV{IS_ONETOUCH}="yes"
ENV{IS_ONETOUCH}=="yes", RUN+="/usr/local/admin/handle-onetouch.sh"
--
ude
Thanks. Where can I find documentation on this REMOVE_CMD thing? Will
two different rules setting the REMOVE_CMD env var override each other?
In addition, what does the syntax := mean? Also, I can't find a rule in
the rules.d directory that deals with this env var.
--
udev calls my script for "ad
You can't match against SYSFS and expect it to work on "remove" since
the sysfs information won't be present.
Use ENV{REMOVE_CMD}:="" on the rule to have the same command run on
remove.
** Changed in: udev (Ubuntu)
Status: New => Invalid
--
udev calls my script for "add" but not for "rem
** Changed in: udev (Ubuntu)
Sourcepackagename: None => udev
--
udev calls my script for "add" but not for "remove"
https://bugs.launchpad.net/bugs/135429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
