Analysis of the upper limit and coverage principle of Windows7 log

The importance of journaling has been deeply rooted. But over time, the space occupied by the entire event log is expanding. To do this you need to set a maximum value for the log file to prevent it from taking up too much hard disk space. This is not only a waste, but it has created some obstacles to reading. And the importance of different log files is different. For this reason, the system administrator determines the maximum upper limit of each log file and the principle of log coverage based on the importance of the log file, hard disk space, and deployment application. In this respect, WINDOWS7 has some improvement over Windows2003. The author then goes on to talk about in the Windows7 if the limit of the log file, will focus on some of its improvements in this area.

As pictured above, this is the admin interface for the Windows7 log file. In the Windows7 operating system, these settings can be defined for each log file. Because there are more log files in the operating system, and each log file specifically records a portion of the content. For this reason its importance, record capacity and so on are different. To do this as a system administrator, you need to understand the content, importance, and so on of each log file, and then determine these control factors based on these situations. For stand-alone operating systems, the log files are often stored in the system disk. Therefore, the log file can not occupy too much space, otherwise it will affect the operating system performance.

First, the maximum set of log files.

System administrators can set up their maximum hard disk space for each log file, respectively. The set method is very simple, just select the corresponding log file, and then click the Right button, and then select Properties, it will pop up this dialog box. You can then see an option called the maximum log size. You can enter the maximum limit for the log file in the following text box. In setting this limit, the main need to pay attention to two aspects of the content.

First, the number entered here must be a multiple of 64. As the 20480 entered above, it is 320 times times 64. If the number we enter here is not a multiple of 64, as entered as 20481, the system prompts the error message: "The increment of the log size value must be 64KB and must be greater than 0." The log size will be set to the minimum multiple of 64KB. When determined, this value is automatically changed to the nearest value of 64 times times. If I enter 20416 and then press OK, this value will automatically become 20416. This restriction system administrator needs to attract some attention.

Second, the log file is not as large as possible. Although the log file is large, you can record all event information. However, it will also bring trouble to the future reading. It's not easy to find what you need in a lot of records. And the log consumes too much system disk space, also can affect the performance of the operating system. For this reason, there is a reasonable limit to the size of this log space. But this is exactly how much appropriate, there is no uniform standard. It is often necessary for the system administrator to determine how much of this log file size is appropriate, based on their own experience and in combination with the specific applications deployed on the operating system. In general, however, the space occupied by the log space on the system disk is best not to exceed 5%.