[Pkg-alsa-devel] Bug#435624: /etc/init.d/udev restart && udevtrigger restores saved ALSA volume

[Timo Lindfors]

Hi,

md at Linux.IT (Marco d'Itri) writes:
>> 5) sudo udevtrigger; sleep 20
> *Never* do this unless you have a very good reason, because it has side 
> effects like this one.

Oh, good to know! I've been under the impression that udevtrigger is
what I should use to apply changes I've made to files in
/etc/udev. Here's an example of how I've previously changed the
ownership of /dev/rtc:

1) Before making any changes rtc is owned by audio group

crw-rw---- 1 root audio 10, 135 Jun 27 08:18 /dev/rtc

2) I then edit /etc/udev/permissions.rules and change

KERNEL=="rtc|rtc[0-9]*",                        GROUP="audio"

into

KERNEL=="rtc|rtc[0-9]*",                        GROUP="video"

3) After saving the file and waiting for a while rtc is still owned by
   audio (http://reactivated.net/writing_udev_rules.html suggested
   that udev could detect changes automatically with inotify):

crw-rw---- 1 root audio 10, 135 Jun 27 08:18 /dev/rtc

4) After issuing sudo /etc/init.d/udev restart and waiting for a while
   rtc is still owned by audio

crw-rw---- 1 root audio 10, 135 Jun 27 08:18 /dev/rtc

5) Finally, when I issue udevtrigger the ownership changes:

crw-rw---- 1 root video 10, 135 Jun 27 08:18 /dev/rtc

I guess the final question is: How should I change the ownership of
/dev/rtc if not by using udevtrigger?

best regards,
Timo Lindfors