Comment # 11 on bug 1078358 from Mario Goppold

(In reply to Mario Goppold from comment #10)
> (In reply to Joey Lee from comment #9)
> > (In reply to Mario Goppold from comment #8)
> > > Here is my Log:
> > > 
> > >   virtserv2:~ # mv /usr/lib/udev/rules.d/80-acpi-container-hotplug.rules
> > > _usr_lib_udev_rules.d_80-acpi-container-hotplug.rules
> > >   virtserv2:~ # awk '/^processor/ {S+=1}END{print S}' /proc/cpuinfo
> > >   24
> > >   virtserv2:~ # udevadm trigger --verbose > udevadm_trigger.log 2>&1
> > >   virtserv2:~ # awk '/^processor/ {S+=1}END{print S}' /proc/cpuinfo
> > >   24
> > >   virtserv2:~ # mv _usr_lib_udev_rules.d_80-acpi-container-hotplug.rules
> > > /usr/lib/udev/rules.d/80-acpi-container-hotplug.rules
> > >   virtserv2:~ # udevadm trigger --verbose > udevadm_trigger_2.log 2>&1
> > >   virtserv2:~ # awk '/^processor/ {S+=1}END{print S}' /proc/cpuinfo 
> > >   4
> > >   virtserv2:~ # awk '/^processor/ {S+=1}END{print S}' /proc/cpuinfo
> > >   1
> > > 
> > > The Logfiles udevadm_trigger.log and udevadm_trigger_2.log looks like the
> > > first attachment and does not differ.
> > 
> > I have checked the src/udev/udevadm-trigger.c code in systemd. It makes
> > sense for "udevadm trigger" triggers the CHANGE event to container because
> > "change" is the default action for "udevadm trigger".
> > 
> > If you still want to use "udevadm trigger" but do not want the
> > 80-hotremove-acpi-container.rules to be triggered. Please run:
> > 
> > $ ln -s /dev/null /etc/udev/rules.d/80-hotremove-acpi-container.rules
> 
> yes, I moved the file away and everything will be ok till the next
> udev-update. 

Ok, i see the rule in /etc/udev/rules.d prevent the system-wide run and so it
is safe from an update.

> I think the rule should be much more special than it is now, maybe with
> vendor or  SUBSYSTEM!="cpu" or ...