Mark Knecht wrote:
>pdflush(185): WRITE block 14947712 on hda3
>syslog-ng(5341): dirtied inode 936889 (messages) on hda3
>syslog-ng(5341): dirtied inode 936889 (messages) on hda3
>kjournald(869): WRITE block 14947712 on hda3
>kjournald(869): WRITE block 9112 on hda3
>kjournald(869): WRITE block 9120 on hda3
>kjournald(869): WRITE block 9128 on hda3
>pdflush(185): WRITE block 14947712 on hda3
>syslog-ng(5341): dirtied inode 936889 (messages) on hda3
>kjournald(869): WRITE block 9136 on hda3
>kjournald(869): WRITE block 9144 on hda3
>syslog-ng(5341): dirtied inode 936889 (messages) on hda3
>syslog-ng(5341): dirtied inode 936889 (messages) on hda3
>
>
>
Yep, syslog is what is causing the disk to spin up.
Have a look at /var/log/messages and see what it is writing out. If it
is messages like this:
Jun 8 19:15:32 carcharias syslog-ng[9232]: STATS: dropped 0
You can stop those by commenting out the "stats" option in
/etc/syslog-ng/syslog-ng.conf. Or if you don't want any messages file
at all (I don't think I would recommend this, BTW), you can change the line:
destination messages { file("/var/log/messages"); };
to be /dev/null.
HTH.
-Richard
--
[email protected] mailing list
