Hello<div><br></div><div>On my laptop I run Arch Linux with syslog-ng and cronie (cron) among other programs of course.</div><div><br></div><div>I'm trying to get my harddrive to spin down automatically once in a while (using hdparm).</div>
<div><br></div><div>Me and a lot of other people both in the Arch and Ubuntu community are having our attempts to do this ruined, by what first seemed to be the EXT4 journalling block device (jbd2).</div><div><br>After long discussions and finally a bug report (see at the bottom of this mail), I think I've boiled my troubles down to be mostly about syslog-ng (and possibly cronie - but I don't think so).</div>
<div><br></div><div>No matter what I try I can't seem to get syslog-ng to stop "waking up my disks" (at least that's what kernel tracing tells me). Killing the crond process almost totally stops these syslog-ng writes to the disk. Unfortunately I've been unable to configure my way out of it using syslog-ng.conf. So my harddrive won't stay spinned down - not even for a minute.</div>
<div><br></div><div>This is what tracing the journalling gives me (see the kernel bug report below for an explanaition):</div><div><a href="http://pastebin.com/raw.php?i=J6BtGVrz">http://pastebin.com/raw.php?i=J6BtGVrz</a></div>
<div><br></div><div>As you can probably see, syslog-ng writes every minute at least. I guess that's because my user crontab has a command that gets run every minute. What I don't get is why syslog-ng writes to the disk, even though I'm telling it not to log crond's output.</div>
<div><br></div><div>Here is my syslog-ng.conf - as you can see I tried to output the crond messages to /dev/null. I guess it works, because there are no mentions of crond anywhere in /var/log anymore.</div><div><a href="http://pastebin.com/raw.php?i=H02KKWPV">http://pastebin.com/raw.php?i=H02KKWPV</a></div>
<div><br></div><div>Here are the discussions and the bug report I mentioned:</div><div><a href="https://bbs.archlinux.org/viewtopic.php?id=113516">https://bbs.archlinux.org/viewtopic.php?id=113516</a></div><div><a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607560">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607560</a></div>
<div><a href="https://bugzilla.kernel.org/show_bug.cgi?id=39072">https://bugzilla.kernel.org/show_bug.cgi?id=39072</a></div><div><br></div><div>I don't know if syslog-ng is causing trouble for only me, but it seems unlikely.</div>
<div><br></div><div>Regards,</div><div>Lars</div>