Source: Chinese Eagle Union
I think it is a good log clearance tool for you to use Xiaoyan's Cleaniislog. But unfortunately, only the log files generated by the IIS, the log files such as FTP and Shedule are generally cleared.
Windows2000 log files typically have application logs, security logs, system logs, DNS server logs, FTP logs, WWW logs, etc., which may be different depending on the service enabled by the server.
The general steps are as follows:
1. Clear the log of IIS.
Don't underestimate the IIS's log feature, which can record your intrusion process, such as the command you play with the Unicode invading, and the traces left when scanning 80 ports. You may be because of its non-payment, but it is stared by the network management, maybe it will be ... huh, huh.
Then we can clear it manually:
1. Default location of the log:% systemroot% / system32 / logfiles / w3svc1 /, default a log. Then let's switch to this directory, then del *. *. You probably want to be safe, then DIR. ...... 咦, 咦, how is today's log? Don't panic! Because the W3SVC service is still open, how can we clear this log file?
Method 1: If there is 3389 can log in, then open with notepad, press Ctrl A and then Del.
Method 2: NET command
C: /> NET STOP W3SVC
The World Wide Web Publishing Service service is being stopped. (May wait for a long time, may also be unsuccessful)
World Wide Web Publishing Service Service has been successfully stopped.
Well, W3SVC stopped, we can empty it, del *. *
Don't forget to open the W3SVC service!
C: /> NET START W3SVC
2. Clear the FTP log
FTP log default location:% systemroot% / sys tem32 / logfiles / msftpsvc1 /, default a log, clear method is the same.
3. Clear the SCHEDULER log
Scheduler Service Log Default Location:% SystemRoot% / Schedlgu.txt. Clear method is the same.
4. Application logs, security logs, system logs, DNS log default location:% systemroot% / sys tem32 / config. Clear method is the same.
Note that the above three directories may not be on the top, that is because the administrator has made modifications. You can read the registry worth getting your location:
Application log, security log, system log, DNS server log, these log files in the registry
HKEY_LOCAL_MACHINE / SYS TEM / CURRENTCONTROLSET / SERVICES / EVENTLOG
Schedluler service log in the registry
HKEY_LOCAL_MACHINE / SOFTWARE / Microsoft / SchedulingAgent
5. I borrowed from other people's articles (actually copying)
OK! Congratulations, now a simple log has been successfully deleted. Here is a difficult security log and system log, guarding these logs is Event log, trying to stop it!
D: / Server / System32 / Logfiles / W3SVC1> NET STOP EVENTLOG
This service cannot accept the "pause" or "stop" operation of the request. No way, it is a key service. If you do not need a third-party tool, you don't delete the security log and system log at all on the command line! So, it is still necessary to use a simple but speed slow crash. Open "Event Viewer" in the "Management Tool" of "Control Panel" (98 is not, know the benefits of Win2K), "Operation" in the menu The item has a menu named "Connect to another computer", click on it and enter the IP of the remote computer, then click on the smoke, wait for dozens of minutes, endure the torture of the crash, finally opened! Then select the security log of the remote computer, right-click on its properties, click the "Clear Log" button in the properties, OK! The safety log is clear! The same endurance pain to clear the system log! 6. Most of the important logs above you have been cleared. Then you have to do it, there is still an omission.
That's doing this:
Some files below DEL:
/Winnt/*.log
System32
/logfiles/*.*
/dtclog/*.*
/config/*.evt
/*.log
/*.TXT
So far, most of my clearing log methods I have learned have chopped you, then you learn to use it.
