on., 10.10.2007 kl. 09.33 -0400, skrev Steve Grubb: > On Wednesday 10 October 2007 09:16:19 Zdenek Prikryl wrote: > > since version 1.0.6, acpid does not use separate file for logging. It uses > > openlog() and vsyslog() instead of own implementation of logging. So > > everything go to /var/log/messages. > > Yes, I have been chatting with upstream since I'm getting about 6-8 events a > second. He claims I'm the only person on the planet that is getting this rate > of events and my BIOS is broken. It makes syslog hard to use for researching > problems, but not unreadable. > > > But it could be dangerous. According to this bug > > https://bugzilla.redhat.com/show_bug.cgi?id=294391, it could lead > > to unreadable /var/log/messages. > > I do not see anything in that bug that tells how it damages or makes syslog > unusable. I find that it floods syslog, but its not unreadable. > > > So there are two options: > > 1. Get back to old style logging (but upstream does not want to) > > 2. In /etc/rsyslog.conf append a filter for acpid, so rsyslog will be > > logging messages form acpid in separate file. > > There's a third option, which I've asked upstream about, make some of these > messages DEBUG and only log abnormal messages at the higher syslog > priorities. IOW, not all messages are of the same importance. Seriously, my > battery being full of power or me connecting to AC power is not a syslog > worthy or any log worthy event unless I'm debugging a problem. > > Upstream is of the opinion that I'm the only person seeing a high rate of > events and doesn't really want to fix it unless others report similar > problems. Am I the only one? > I don't see many events per second, but still acpid is flooding syslog: [root@localhost log]# tail -f /var/log/messages Oct 11 09:42:26 localhost acpid: notifying client 2145[0:0] Oct 11 09:42:26 localhost acpid: completed event "thermal_zone TZ0 00000081 00000000" Oct 11 09:42:27 localhost acpid: received event "thermal_zone TZ0 00000081 00000000" Oct 11 09:42:27 localhost acpid: notifying client 2001[68:68] Oct 11 09:42:27 localhost acpid: notifying client 2145[0:0] Oct 11 09:42:27 localhost acpid: completed event "thermal_zone TZ0 00000081 00000000" Oct 11 09:42:41 localhost acpid: received event "thermal_zone TZ0 00000081 00000000" Oct 11 09:42:41 localhost acpid: notifying client 2001[68:68] Oct 11 09:42:41 localhost acpid: notifying client 2145[0:0] Oct 11 09:42:41 localhost acpid: completed event "thermal_zone TZ0 00000081 00000000" Oct 11 09:43:00 localhost acpid: received event "thermal_zone TZ0 00000081 00000000" Oct 11 09:43:00 localhost acpid: notifying client 2001[68:68] Oct 11 09:43:00 localhost acpid: notifying client 2145[0:0] Oct 11 09:43:00 localhost acpid: completed event "thermal_zone TZ0 00000081 00000000" Oct 11 09:43:43 localhost acpid: received event "thermal_zone TZ0 00000081 00000000" Oct 11 09:43:43 localhost acpid: notifying client 2001[68:68] Oct 11 09:43:43 localhost acpid: notifying client 2145[0:0] Oct 11 09:43:43 localhost acpid: completed event "thermal_zone TZ0 00000081 00000000" Oct 11 09:44:16 localhost acpid: received event "thermal_zone TZ0 00000081 00000000" Oct 11 09:44:16 localhost acpid: notifying client 2001[68:68] Oct 11 09:44:16 localhost acpid: notifying client 2145[0:0] Oct 11 09:44:16 localhost acpid: completed event "thermal_zone TZ0 00000081 00000000" Oct 11 09:44:57 localhost acpid: received event "thermal_zone TZ0 00000081 00000000" Oct 11 09:44:57 localhost acpid: notifying client 2001[68:68] Oct 11 09:44:57 localhost acpid: notifying client 2145[0:0] Oct 11 09:44:57 localhost acpid: completed event "thermal_zone TZ0 00000081 00000000" Do we really neew to log all these? Cheers Kjartan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list