|
And just so you do not think I am making
this up here is the public reference that documents it: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/5a86ab0f-c7eb-45ed-9e5e-514173bf15e3.mspx
:-) Thanks, -Steve From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of This problem is described in http://support.microsoft.com/default.aspx?scid=kb;en-us;312571
. The fix allows the automatic archiving of the log files but does not
explain why the problem occurs. The issue is around the fact that a
contiguous block of memory is needed for all of the log files and this is not
pre-allocated so if the memory on the box becomes fragmented, which it will,
then eventually the contiguous block can not be allocated and we will stop
logging. Generally we recommend not setting the total size of all logs
over 300 MB and using the feature above for the security log so that it can be
automatically archived. Thanks, -Steve From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
|
- RE: [ActiveDir] Security Log file size not reaching the max... Daniel Gilbert
- RE: [ActiveDir] Security Log file size not reaching th... Steve Linehan
- RE: [ActiveDir] Security Log file size not reaching th... Free, Bob
