2012/8/8 Kay Sievers : > On Wed, Aug 8, 2012 at 10:07 AM, Alexey Shabalin wrote: >> After run dmesg i can see >> [434765.990649] systemd-udevd[1186]: invalid rule >> '/etc/udev/rules.d/90-alsa-tools-firmware.rules:11' >> [485891.443571] systemd-udevd[1186]: invalid rule >> '/etc/udev/rules.d/90-alsa-tools-firmware.rules:11' >> >> Yes, i know about invalid rule. (need change "BUS" to "SUBSYSTEM") >> Issue - why in dmesg? >> I expected to see in syslog only. > > It doesn't do that here, it's all in the journal only. > > We should only write the udev startup and the network interface > renaming messages to kmsg, nothing else unless asked for.
Thanks for the answer. There are more havy cases. Lots of messages like these: [ 829.590573] systemd-udevd[7033]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory And system have big LA. I know that udev_monitor_new_from_socket() is no longer supported, and i know that necessary to remove old packages like hal and DeviceKit. Whether the udev can behave quieter? Without a heavy LA? Do not write to dmesg. Write to syslog is not often. -- Alexey Shabalin _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
