<br><br><div class="gmail_quote">On Thu, Jun 4, 2009 at 6:38 PM, Steve Freegard <span dir="ltr"><<a href="mailto:steve.freegard@fsl.com">steve.freegard@fsl.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Alex Neuman wrote:<br>
> you mentioned asynchronous logging... Can you point us to a FAQ or a<br>
> description of how this works, and why it's a good thing? Any cons?<br>
<br>
</div>I believe this is already in the MAQ/Wiki.<br>
<br>
To enable asynchronous logging you change your syslog.conf entry from:<br>
<br>
mail.* /var/log/maillog<br>
<br>
to<br>
<br>
mail.* -/var/log/maillog<br>
<br>
On a mail server this can have a considerable effect on performance as<br>
syslog doesn't run sync() calls after each write and therefore allows<br>
the kernel to manage the writes to disk which can have a considerable<br>
advantage for disk IO but with the disadvantage that if the machine<br>
crashes or loses power that you'll be missing some of the most recent<br>
log entries. As part of any performance tuning - I *always* enable this.<br>
</blockquote><div><br>Apart from this, I have found that moving to XFS or ext4 (if you have the courage) makes queue handling pretty fast. With the 24 GB RAM, I am considering having my hold queue on the tmpfs. This though carries the risk of mail loss in case of an power outage for which I have sufficient arrangements. Has anyone used other filesystems such as JFS or Reiser or even ext2? What's your experience?<br>
<br><br>--<br>Zaeem <br></div></div><br>