DebugDiag 1.0

[ 2005/06/01 15:31 | by gOxiA ]

从微软MVP:Bernard Cheah先生那里得知微软发布了一款新工具,用来调试维修IIS,这为IIS管理员带来了惊喜和福音。

**Microsoft releases Debug Diagnostics 1.0 - Release Candidate 1**
 
Microsoft is working diligently on a new tool designed to make the life easier for IIS administrators and developers who are tasked with solving complex problems such as crashes, hangs, or memory leaks.  The tool, called Debug Diagnostics 1.0, is the next generation debugging utility that extends on the functionality of previous tools such as IIS Debug Toolkit 1.1, Debug Matrix, and IIS State.  This tool will be the only fully supported tool for debugging applications that run on IIS upon release and is supported on the IIS 4.0, 5.0, 5.1, and 6.0 platforms. 
 
To join the beta and provide invaluable feedback to the designers,
please do the following -
1. Go to
http://beta.microsoft.com
2. Login in with your passport id.
3. Login using the guest ID "DebugDiag" (it's case sensitive)
4. Click on the "IIS Debug Diagnostic Tool" link.
5. On the left hand side expand survey and select "IIS Debug Diagnostic Tool Nomination Form"
Note: if the customer only wants DebugDiag and doesn't want to sign up for the beta they can do this by selecting "Click here to download IIS Debug Diagnostic Tool" from the File Downloads section.
*You may be prompted to install an activeX control

This tool is also receiving full support via newsgroups which are available by doing the following -
To access WebNews newsgroups:
1. Connect to
http://webnews.microsoft.com
3. For account name, enter "<Your Beta ID>"
4. Enter your Newsgroup Password (if you do not have a Newsgroup password - you can create it on BetaPlace by selecting Modify Your Info from the top navigation bar). Click OK.
5. Select the Program Name or particular newsgroup on the left pane to access.

To provide bug and customer feedback, please open bugs via the beta.microsoft.com using your Microsoft Passport.  It would be incredibly powerful for us to get your feedback and make a true difference in your lives and Microsoft's.

DoScan.exe causes high CPU usage

Situation:
You installed Symantec AntiVirus Corporate Edition 10.0. After you restart the computer, you notice that the process DoScan.exe is using a large amount of CPU and memory. After the DoScan.exe process completes, the Rtvscan.exe process is using about 40 MB of memory.

Solution:
Symantec is investigating this problem to determine a solution. This document will be updated when new information or a solution is available.


The DoScan.exe process is part of the default startup Quick Scan that runs after a user logs on. You cannot disable this Quick Scan using Symantec System Center.

Workarounds
You can prevent the creation of the startup Quick Scan on new Symantec AntiVirus clients by importing a registry file. Follow the directions that apply to your situation.

To remove the startup Quick Scan on Symantec AntiVirus clients
Stop any scans that are currently running, and then download and import the RemoveStartScan.reg file. To download the RemoveStartScan.reg file, click the following icon:

To prevent the creation of the startup Quick Scan before installing clients
Before installing or migrating managed clients, download and import the PreventStartScan.reg file to each client.


Notes:
  • Using the RemoveStartScan.reg file on a Symantec AntiVirus client removes all user-created scans. Users must re-create any scans they created after importing the registry file.
  • Both of these files only work for the currently logged in user. On computers with more than one user, each user must log on and import the file(s).

原文地址:http://service1.symantec.com/SUPPORT/ent-security.nsf/14ad416970eb952688256fc700654269/d908f24bf3de4fa188256ff0006031b7?OpenDocument&src=bar_sch_nam

一般情况下将Linux FC3作为网站服务器用的话,图形界面就不是那么重要,所以要做一些修改,使之启动后进入文本方式。

步骤:

修改etc/inittab文件

找到

id:5:initdefault

改为

id:3:initdefault

完成

很简单,但是不经常用Linux,所以总忘记,特此记录下来!

分页: 448/474 第一页 上页 443 444 445 446 447 448 449 450 451 452 下页 最后页 [ 显示模式: 摘要 | 列表 ]