On Sun, Jun 26, 2011 at 04:26:00PM +0200, Marco d'Itri wrote: > On Jun 26, Jurij Smakov <[email protected]> wrote: > > > I see in the logs that during the installation of the base system > > rsyslog is configured soon after udev. It might be that before rsyslog > > is configured, the logging priorities are not honored. Depending on > > rsyslog (or, perhaps, system-log-daemon | rsyslog) should be a simple > > workaround. > No, this check happens inside udev(adm).
I'm not sure what you mean. As far as I can tell, the messages are logged by udevadm, which is invoked in the postinst of udev package during package configuration. As rsyslog is unpacked but not configured at this point (it is configured later), I presume that logging priority is not honored and messages end up on the system console. If udev package would defend on rsyslog, it would guarantee that rsyslog is configured before udev is, and it might fix things (I have to admit that it's all pure speculation, as I don't really see what special things rsyslog package configuration does). Best regards, -- Jurij Smakov [email protected] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
