Bug 136859

add something like this to /etc/syslog-ng.conf.in and call SuSEconfig afterwards:

seife@susi:/etc/syslog-ng> diff -u syslog-ng.conf.in.orig syslog-ng.conf.in
--- syslog-ng.conf.in.orig      2005-09-26 11:37:33.000000000 +0200
+++ syslog-ng.conf.in   2005-11-17 18:32:36.000000000 +0100
@@ -67,4 +67,6 @@

+filter f_acpid      { match('^\[acpid\]:'); };
 filter f_messages   { not facility(news, mail) and not
filter(f_iptables) and not filter(f_acpi_semaphore); };
 filter f_warn       { level(warn, err, crit) and not filter(f_iptables); };
 filter f_alert      { level(alert); };
@@ -124,6 +125,11 @@
 destination mail { file("/var/log/mail"); };
 log { source(src); filter(f_mail); destination(mail); };

+#
+# acpid messages in one file:
+#
+destination acpid { file("/var/log/acpid"); };
+log { source(src); filter(f_acpid); destination(acpid); flags(final); };

 #
 # Cron-messages in one file:

This will be in one of the next syslog-ng package versions.

that change to syslog-ng.conf.in worked.  I then tried to make /var/log/acpid a symlink to /dev/null.  This didn't work too well, because syslog then chmod'd /dev/null to 0640, which broke a lot of things (can't log into desktop anymore).  :)

well, /var/log/acpid is the same file acpid always logged to, so syslog now does the same (although with a very slightly different format)
You can probably just drop the messages in sylog, but they are not that much that this would really bring any benefit, or am i overlooking something?

ah, ok. i see, the battery argument.
Well, let me assure you that harddisk spinup/down is practically irrelevant for battery lifetime (an idle laptop disk draws ~0.65W, a spun down drive draws ~0.25W. Your machine draws ~15, so the 0.4W amount for ~8:13 minutes (on my panasonich, which has a 75Wh battery. Do not forget, that the disk will never be spun down for the whole runtime, at least not if you actually want to do something on this machine and that you will need additional power to spin up the disk).

I think, this is yours Stefan. Perhaps you can add a filter
to leave out some of the messages.

i already checked in the acpid rule to syslog-ng. /var/log/acpid is not written with fsync(yes) and my harddisk is spinning down happily ever after.

Bart, since beta3 the powersaved stuff should actually work, so if you set the harddisk mode to "aggressive_powersave" in your scheme file, it should spin down. Note: this is not the "advanced powersave" scheme, which might crash the machine. Only the setting for the disk...

In RC1, /var/log/messages is still flooded by acpid messages :-(
(>2/3 of the lines are caused by acpid!)

/var/log/acpid does not even exist.

/etc/syslog-ng/syslog-ng.conf.in is unmodified (according to rpm --verify), the generated syslog-ng.conf only has some additional unix-dgram entries. Both contain your change from comment #1 - but it seems it is not working :-(

since it seems to work for everybody else, we need more information.
Please provide:
- rpm -V syslog-ng
- /etc/syslog-ng.conf{.in,}
- some acpid lines from /var/log/messages

cb@cboltz:~> rpm -V syslog-ng
S.5....T  c /etc/syslog-ng/syslog-ng.conf
cb@cboltz:~>



the newest lines from /var/log/messages:
Apr 15 12:32:38 cboltz [acpid]: received event "battery BAT1 00000080 00000001"
Apr 15 12:32:38 cboltz [acpid]: notifying client 3608[0:0]
Apr 15 12:32:38 cboltz [acpid]: notifying client 3838[0:0]
Apr 15 12:32:38 cboltz [acpid]: notifying client 4291[0:0]
Apr 15 12:32:38 cboltz [acpid]: completed event "battery BAT1 00000080 00000001"
Apr 15 12:32:38 cboltz [acpid]: received event "battery BAT2 00000080 00000000"
Apr 15 12:32:38 cboltz [acpid]: notifying client 3608[0:0]
Apr 15 12:32:38 cboltz [acpid]: notifying client 3838[0:0]
Apr 15 12:32:38 cboltz [acpid]: notifying client 4291[0:0]
Apr 15 12:32:38 cboltz [acpid]: completed event "battery BAT2 00000080 00000000"
Apr 15 12:33:39 cboltz [acpid]: received event "battery BAT1 00000080 00000001"
Apr 15 12:33:39 cboltz [acpid]: notifying client 3608[0:0]
Apr 15 12:33:39 cboltz [acpid]: notifying client 3838[0:0]
Apr 15 12:33:39 cboltz [acpid]: notifying client 4291[0:0]
Apr 15 12:33:39 cboltz [acpid]: completed event "battery BAT1 00000080 00000001"
Apr 15 12:33:39 cboltz [acpid]: received event "battery BAT2 00000080 00000000"
Apr 15 12:33:39 cboltz [acpid]: notifying client 3608[0:0]
Apr 15 12:33:39 cboltz [acpid]: notifying client 3838[0:0]
Apr 15 12:33:39 cboltz [acpid]: notifying client 4291[0:0]
Apr 15 12:33:39 cboltz [acpid]: completed event "battery BAT2 00000080 00000000"
Apr 15 12:34:40 cboltz [acpid]: received event "battery BAT1 00000080 00000001"
Apr 15 12:34:40 cboltz [acpid]: notifying client 3608[0:0]
Apr 15 12:34:40 cboltz [acpid]: notifying client 3838[0:0]
Apr 15 12:34:40 cboltz [acpid]: notifying client 4291[0:0]
Apr 15 12:34:40 cboltz [acpid]: completed event "battery BAT1 00000080 00000001"
Apr 15 12:34:40 cboltz [acpid]: received event "battery BAT2 00000080 00000000"
Apr 15 12:34:40 cboltz [acpid]: notifying client 3608[0:0]
Apr 15 12:34:40 cboltz [acpid]: notifying client 3838[0:0]
Apr 15 12:34:40 cboltz [acpid]: notifying client 4291[0:0]
Apr 15 12:34:40 cboltz [acpid]: completed event "battery BAT2 00000080 00000000"

Created attachment 78599 [details]
/etc/syslog-ng/syslog-ng.conf

Created attachment 78600 [details]
/etc/syslog-ng/syslog-ng.conf.in

are you using syslog-ng at all?
"chkconfig syslogd"
"chkconfig syslog-ng"

ok, that's wrong :-)
"grep SYSLOG_DAEMON /etc/sysconfig/syslog"
determines if syslogd or syslog-ng is used.

# grep SYSLOG_DAEMON /etc/sysconfig/syslog
SYSLOG_DAEMON="syslogd"

Good guess...
OK, then the syslog-ng configfile might be correct ;-)

# rpm -q syslogd
syslogd-1.4.1-555

# rpm -V syslogd
does not give any output.

Can you change /etc/syslogd.conf as well?

no, syslogd does not provide the needed functionality. This is why syslog-ng is default now ;-)
Closing as fixed, if you disagree file a bug under "update problems".

Maybe we should mention in the release notes that after an update manual selection of syslog-ng is recommended.

(In reply to comment #15)
> no, syslogd does not provide the needed functionality. This is why syslog-ng 
> is default now ;-)

OK, I just switched to syslog-ng ;-)

> Maybe we should mention in the release notes that after an update manual
> selection of syslog-ng is recommended.

Good idea - bug 166932 (hello AJ ;-)

I also noticed that syslogd was not stopped after switching to syslog-ng and "rcsyslog restart" :-( - bug 166933

Finally: I can verify that /var/log/messages is no longer flooded with acpid messages :-)

Thanks for your help!