<br><br><div class="gmail_quote">2010/2/25 Igor Sysoev <span dir="ltr"><<a href="mailto:igor@sysoev.ru">igor@sysoev.ru</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Feb 25, 2010 at 01:16:04PM +0800, yong xue wrote:<br>
<br>
> The *access_log* directive sets the path, format and buffer size for the<br>
> access log file. Using "off" as the only parameter clears all<br>
> *access_log* directives<br>
> for the current level. If the format is not indicated, it defaults to<br>
</div>> "combined" <<a href="http://wiki.nginx.org/NginxHttpLogModule#log_format_combined" target="_blank">http://wiki.nginx.org/NginxHttpLogModule#log_format_combined</a>>.<br>
<div class="im">> The size of buffer must not exceed the size of the atomic record for writing<br>
> into the disk file. This size is not limited for FreeBSD 3.0-6.0.<br>
><br>
> this is quoted from <a href="http://wiki.nginx.org" target="_blank">wiki.nginx.org</a>.<br>
> My server is running linux 2.6.16.<br>
> I dont know the size of the atomic record for writing into the disk file.<br>
> Can somebody help me?<br>
><br>
> I googled, but cannot make sure that the linux write system call is atomic.<br>
<br>
</div>Linux shell ensure atomic write for PIP_BUF, i.e. 4K. However, I believe<br>
this value is much more for regular files, so you may try to set 32k.<br>
<font color="#888888"><br>
<br></font></blockquote><div>thanks.</div><div><br></div><div>so the size depends on the implementation. And the access log is not much serious. </div><div>I will do some reading on the kernel later if i have time. </div>
</div><br clear="all"><br>-- <br>Best Regards,<br><br>Ѧ ÓÂ<br><br>QQ:312200<br><br><a href="mailto:e-mail%3Aultraice@gmail.com">e-mail:ultraice@gmail.com</a><br><a href="mailto:MSN%3Ait@easy-boarding.com">MSN:it@easy-boarding.com</a><br>