제2의 비엔지니어 인생관을 꿈꾸며

Posted
Filed under Study


https://blogs.technet.microsoft.com/askpfeplat/2012/12/09/why-adding-hyper-v-replica-connection-broker-fails-in-failover-cluster-manager/
사용자 삽입 이미지

MSCS 환경에서 복제본 브로커 등록할때 실패가 떨어지는 경우가 간혹 있습니다.
사용자 삽입 이미지

수동으로 복제본 브로커 컴퓨터 개체를 만들고 속성에 보안탭에 MSCS 클러스터 컴퓨터 개체를 등록해주고 풀권한을 주고 확인을 주면 해결이 됩니다.
사용자 삽입 이미지
이방법은 복제본 브로커 등록 실패뿐만이 아니고 MSSQL 사전설치 DTC 구성시에도 등록실패가 발생하는 경우도 간혹 있습니다. 이와 같은 방법으로 클러스터 컴퓨터 개체의 권한을 등록시켜줘서 자동으로 업데이트 되게 하는 방법이 있습니다.
위에 링크에는 두번째 방법  특정권한을 위임해주는 방법도 존재합니다만 전 첫번째 옵션 방법이 단번에 해결되어서 두번째 방법까지 쓸 경우가 없었습니다.
2017/01/08 04:02 2017/01/08 04:02
Posted
Filed under Study
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033250

Purpose

In the majority of environments, you must not change VMware High Availability (HA) default settings. However, depending on your specific environment, you must modify some HA options.

This article describes the different configuration options available and how to apply them.

Resolution

Note: Not all configuration variables work in all versions of vCenter Server. As new variables are introduced in newer releases, they remain throughout later versions.

Applying a VMware HA customization

Using the vSphere Web Client

  1. Log in to VMware vSphere Web Client.
  2. Go to Home > vCenter > Clusters.
  3. Under Object, click on the cluster you want to modify.
  4. Click Manage.
  5. Click vSphere HA.
  6. Click Edit.
  7. Click Advanced Options.
  8. Click Add and enter in Option and Value fields as appropriate (see below).
  9. Deselect Turn ON vSphere HA.
  10. Click OK.
  11. Wait for HA to unconfigure, click Edit and check Turn ON vSphere HA.
  12. Click OK and wait for the cluster to reconfigure.
Using the vSphere Client
  1. Log in to vCenter Server with vSphere Client as an administrator.
  2. Right-click the Cluster in the Inventory and click Edit Settings.
  3. Click VMware HA.
  4. Click Advanced Options.
  5. Enter Option and Value fields as appropriate (see below).
  6. Click OK.
  7. Click OK again.
  8. Wait for the Reconfigure Cluster task to complete and right-click the Cluster again from the Inventory.
  9. Click Properties.
  10. Disable VMware HA and wait for the Reconfiguration Cluster task(s) to complete.
  11. Right-click the cluster and Enable VMware HA to have the settings take effect.

    Note: See below if reconfiguration of the hosts is necessary.

There are three types of HA advanced options and each is set in a different way.

  • vCenter Server options (VC) -- these options are configured at the vCenter Server level and apply to all HA clusters unless overridden by cluster-specific options in cases where such options exist. If the vCenter Server options are configured using the vCenter Server options manager, a vCenter Server restart may not be required -- see the specific options for details. But if these options are configured by adding the option string to the vpxd.cfg file (as a child of the config/vpxd/das tag), a restart is required.
  • Cluster options (cluster) -- these options are configured for an individual cluster and if they impact the behavior of the HA Agent (FDM), they apply to all instances of FDM in that cluster. These options are configured by using the HA cluster-level advanced options mechanism, either via the UI or the API. Options with names starting with "das.config." can also be applied using the "fdm options" mechanism below, but this is not recommended because the options should be equally applied to all FDM instances.
  • fdm options (fdm) -- these options are configured for an individual FDM instance on a host. They are configured by adding the option to the/etc/opt/vmware/fdm/fdm.cfg file of the host as a child of the config/fdm tag. Options set in this way are lost when fdm is uninstalled (for example if the host is removed from vCenter Server and then re-added) or if the host is managed by Auto Deploy and is rebooted.

Common Options

Version

Name

Description

Reconfiguration

Type of Option

Cluster Configuration

5.0, 5.1, 5.5

das.allowNetworkX

Allows you to specify the specific management networks used by HA, where X is a number between 0 and 9. For example if you set a value to ʺManagement Networkʺ, only the networks associated with port groups having this name are used. Ensure that all hosts are configured with the named port group and the networks are compatible. In 5.5, this option is ignored if vSAN is enabled for the cluster.

Yes. Reconfigure HA on all hosts to have the specification take effect.

Cluster

5.0, 5.1, 5.5

das.ignoreRedundantNetWarning

HA will report a config issue on a host if the host is not configured with redundant networks for the networks used by HA. Prior to 5.5, HA only uses management networks, while in 5.5, if vSAN is enabled, HA will use the networks configured for vSAN. Valid values are true/false. Set to true to suppress the config issue. False is assumed if the option is not set. 

Yes. Reconfigure HA on a host to have the config issue for that host cleared.

Cluster

5.0, 5.1, 5.5, 6.0

das.heartbeatDsPerHost

HA chooses by default 2 heartbeat datastores for each host in an HA cluster. This option can be used to increase the number to a value in the range of 2 to 5 inclusive.

Yes. Reconfigure HA on all hosts in the cluster.

Cluster

5.0, 5.1, 5.5, 6.0

das.ignoreInsufficientHbDatastore

HA will report a host config issue if it was not able to select the required number of datastores for a host given by das.heartbeatDsPerHost. Set this option to true to suppress this warning, and false to enable it. A value of false is assumed if the option is not set.

Yes. Reconfigure HA on all hosts in the cluster.

Cluster

5.0, 5.1, 5.5

das.includeFTcomplianceChecks

Whether to check the cluster for compliance with Fault Tolerance as part of the cluster profile compliance check. Set this option to false if you don't plan to use FT in the cluster. A value of true enables the checks. If unset, a value of true is assumed.

No

Cluster

5.5 U3 vpxd.das.fdmWaitForUpdatesTimeoutSec Timeout period for which HA waits for a response from the FDM master node.

Note:  This setting needs to be applied from the vCenter Server Advanced Settings.  For more information. see the Configure Advanced Settings in the vSphere Web Client section of the vCenter Server and Host Management guide.
Yes,  vCenter Server needs to be restarted. VC

Admission Control

5.0, 5.1, 5.5

das.vmMemoryMinMB

Value in MB to use for the memory reservation of a virtual machine if no non-zero memory reservation is set by a user. 0 is assumed if the option is not set.

No

Cluster

5.0, 5.1, 5.5

das.vmCpuMinMHz

Value in MHz to use for the CPU reservation of a virtual machine if no non-zero CPU reservation are set by a user. 32 is assumed if the option is not set.

No

Cluster

5.0, 5.1, 5.5, 6.0

das.slotCpuInMHz

Maximum value in MHz to use for CPU component of the slot size. No limit is imposed if the option is not set. In 5.1, the CPU component of the slot size can be exactly specified in the UI and the API (see the vim.cluster.slotPolicy object). Note that this option and the UI/API behave differently -- this option sets a max while the UI/API sets the exact value. If a slot policy is defined and this option is specified, the value specified by this option is ignored.

No

Cluster

5.0, 5.1, 5.5, 6.0

das.slotMemInMB

Maximum value in MB to use for memory component of the slot size. No limit is imposed if the option is not set. In 5.1, the memory component of the slot size can be exactly specified in the UI and the API (see the vim.cluster.slotPolicy object). Note that this option and the UI/API behave differently -- this option sets a max while the UI/API sets the exact value. If a slot policy is defined and this option is specified, the value specified by this option is ignored.

No

Cluster

6.0 das.config.fdm.memreservationmb  By default vSphere HA agents run with a configured memory limit of 250 MB. A host might not allow this reservation if it runs out of reservable capacity. You can use this advanced option to lower the memory limit to avoid this issue. Only integers greater than 100, which is the minimum value, can be specified. Conversely, to prevent problems during master agent elections in a large cluster (containing 6,000 to 8,000 VMs) you should raise this limit to 325 MB.

Note: Once this limit is changed, for all hosts in the cluster you must run the Reconfigure HA task. Also, when a new host is added to the cluster or an existing host is rebooted, this task should be performed on those hosts in order to update this memory setting.
No Cluster

Restarting virtual machines

5.0, 5.1, 5.5

das.maxvmrestartcount

The maximum number of times an FDM master will try to restart a virtual machine before giving up. Five attempts are made if this option is unset. This limit only applies if the time since the first restart attempt was made is less than das.maxvmrestartperiod. Note that FT secondary virtual machine restarts are governed by the separate parameter, das.maxftvmrestartcount.
Warning: Setting this value to a very high number creates a large amount of extra logging which can have an impact on your system log directories.

No

Cluster

5.0, 5.1, 5.5

das.maxvmrestartperiod

The maximum amount of time (in seconds) during which a FDM master will attempt to restart a virtual machine after the first restart attempt failed. The time is measured from when the FDM master first tried to restart the virtual machine. This time limit takes precedence over das.maxvmrestartcount. No time limit is imposed if this option is unset.

No

Cluster

5.0, 5.1, 5.5

das.maxftvmrestartcount

The maximum number of times an FDM master will try to start a secondary virtual machine for an FT virtual machine pair before giving up. Five attempts are made if this option is unset.
Warning: Setting this value to a very high number creates a large amount of extra logging which can have an impact on your system log directories

No

Cluster

5.0U1, 5.1, 5.5

das.maskCleanShutdownEnabled

When a virtual machine powers off and its home datastore is not accessible, HA cannot determine whether the virtual machine should be restarted. So, it must make a decision. If this option is set to false, the responding FDM master will assume the virtual machine should not be restarted, while if this option is set to true, the responding FDM will assume the virtual machine should be restarted. If the option is unset in 5.0U1, a value of false is assumed, whereas in ESXi 5.1 and later, a value of true is assumed.

No

Cluster

5.5, 6.0 das.respectVmVmAntiAffinityRules Respect vm-vm anti-affinity rules when restarting virtual machines after a failure. The valid values are "false" (default) and "true" No Cluster
6.0 das.maxresets The maximum number of reset attempts made by VMCP. If a reset operation on a virtual machine affected by an APD situation fails, VMCP retries the reset this many times before giving up. No Cluster
6.0 das.maxterminates The maximum number of retries made by VMCP for virtual machine termination. No Cluster
6.0 das.terminateretryintervalsec If VMCP fails to terminate a virtual machine, this is the number of seconds the system waits before it retries a terminate attempt. No Cluster
6.0 das.reregisterRestartDisabledVMs
When vSphere HA is disabled on a specific virtual machine this option
ensures that the virtual machine is registered on another host after a
failure. This allows you to power-on that virtual machine without
needing to re-register it manually.
Note: When this option is used, vSphere HA does not
power on the virtual machine, but only registers it.
No Cluster

Isolation Response

5.0, 5.1, 5.5, 6.0

das.isolationAddressX

IP addresses an FDM agent uses to check for isolation when no agent network traffic is observed on the network(*) used by HA, where X = 0-9. HA will use the default management-network gateway as an isolation address by default plus those specified by this advanced option as additional addresses to check. We recommend adding an isolation address for each management network used by HA.(*) Prior to 5.5, HA uses only the management network, but in 5.5 when vSAN is also enabled on the cluster, HA will use the vSAN network for inter-agent communication.

No

Cluster

5.0, 5.1, 5.5, 6.0

das.useDefaultIsolationAddress

Whether the default isolation address (gateway of management network) should be used when determining if a host is network isolated. Valid values are true/false. By default, the management network default gateway is used. If the default gateway is a non-pingable address, set the “das.isolationaddressX” to a pingable address and disable the usage of the default gateway by setting this option to “false”.

No

Cluster

5.1, 5.5, 6.0

das.config.fdm.isolationPolicyDelaySec

The number of seconds an FDM agent waits before executing the isolation policy once it has determined that the host is isolated. The minimum value is 30. If set to a value less than 30, the delay is 30 seconds.

No

Cluster

5.0, 5.1, 5.5, 6.0

das.isolationShutdownTimeout

The number of seconds an FDM waits for a virtual machine to power off after initiating a guest shutdown before the FDM issues a power off. If the option is unset, 300s is used.

No

Cluster

6.0 das.config.fdm.reportfailoverfailevent When set to 1, enables generation of a detailed per-VM event when an attempt by vSphere HA to restart a virtual machine is unsuccessful. Default value is 0. In versions earlier than vSphere 6.0, this event is generated by default. No Cluster

Virtual machine/App Monitoring

5.0, 5.1, 5.5, 6.0

das.iostatsInterval

If an FDM detects that a sufficient number of VMtools heartbeats are missing to trigger a virtual machine's configured virtual machine/App monitoring policy, the FDM checks if any I/O have been issued in the last ioStatsInterval, and will only reset the virtual machine if no I/O occurred in this interval. Values of 0 or greater are valid. 120s is assumed if the option is unset.

No

Cluster

Fault Tolerance

5.0, 5.1, 5.5

das.maxFtVmsPerHost

Specifies the number of Fault Tolerance virtual machines that can be run on a host at one time. If unset, a value of 4 is used. A value of -1 or 0 disables the limit. The limit is enforced by vCenter Server when executing user initiated power ons and vmotions, and by DRS when doing initial placement and load balancing. HA does not enforce this limit to maximize uptime. DRS does not correct any violations of this limit.

No

Cluster

Logging

5.0, 5.1, 5.5

das.config.log.maxFileNum

Controls the number of FDM log-file rotations retained by the FDM file-based logger. The file-based logger is used by default only by the FDM when running on ESX versions earlier than ESX 5.0. If you wish to change the number of log-file rotations maintained for a pre ESX 5.0 host, set this option to the desired number of log files. For ESX 5.0 and later hosts, the FDM logs to syslog by default and so you need to use the syslog configuration mechanism to change the amount of retained logging history. However, it is possible to enable the file-based logger for ESXi 5.0 and later hosts hosts also. To do so, set this option to a valid value. If you are using vSphere 5.0 Update 1 or later, you must also set the option das.config.log.outputToFiles to true. For all ESX versions, setting the option das.config.log.maxFileNum to 1 will disable the log-file rotations. The location of log files can be changed using the option das.config.log.directory.

Yes

Cluster

5.0, 5.1, 5.5

das.config.log.maxFileSize

Controls the size of each log file written out by the FDM file-based logger. Files are 1 MB in size unless this option is specified. This option is used in conjunction with das.config.log.maxFileNum to control the log history.

Yes

Cluster

5.0, 5.1, 5.5

das.config.log.level

Controls the amount of information recorded in the logs based on severity levels None, Warning, Info, Verbose, and Trivia.

Yes

Cluster

 

2016/12/10 00:36 2016/12/10 00:36
Posted
Filed under Study
https://buildnumbers.wordpress.com/

SQL Server build numbers

SSMS – SQL Server Management Studio

 

  RTM SP1 SP2 SP3 SP4 Latest
SQL Server vNext           14.0.1.246 (CTP1)
SQL Server 2016 13.00.1601.5 13.0.4001.0       13.0.4001.0 (SP1)
SQL Server 2014 12.00.2000.8 12.00.4100.1 12.00.5000     12.00.5532.0 (MS16-136)
SQL Server 2012 11.00.2100.60 11.00.3000 11.00.5058 11.00.6020   11.00.6567.0 (MS16-136)
SQL Server 2008R2 10.50.1600.1 10.50.2500 10.50.4000 10.50.6000   10.50.6542 (TLS 1.2 upd)
SQL Server 2008 10.00.1600.22 10.00.2531 10.00.4000 10.00.5500 10.00.6000 10.00.6547 (TLS 1.2 upd)
SQL Server 2005 9.00.1399.06 9.00.2047 9.00.3042 9.00.4035 9.00.5000 9.00.5324 (MS12-070)
SQL Server 2000 8.00.194 8.00.384 8.00.532 8.00.760 8.00.2039 8.00.2305 (MS12-060)
SQL Server 7.0 7.0.623 7.0.699 7.0.842 7.00.961 7.00.1063 7.00.1152 (MS08-040)
SQL Server 6.5 6.50.201 See below 6.50.416 (SP5a)
SQL Server 6.0 6.00.121 6.00.124 6.00.139 6.00.151   6.00.151 (SP3)

Office build numbers

Office 2016

Build Number (MSO) KB Description
16.0.4229.1024   Office 2016 RTM
16.0.4266.1003   Office 2016 RTM (Volume license)

Office 2013

Build Number (MSO) KB Description
15.0.4420.1017   Office 2013 RTM
15.0.4569.1506 KB2850036 Office 2013 SP1 32-bit 64-bit

Office 2010

Build Number (MSO) KB Description
14.0.4760.1000   Office 2010 RTM
14.0.6023.1000 KB2510690 Office 2010 SP1 32-bit 64-bit
14.0.7015.1000 KB2687521 Office 2010 SP2 32-bit 64-bit

Office 2007

Build Number (MSO) KB Description
12.0.4518.1014   Office 2007 RTM
12.0.6213.1000 KB936982 Office 2007 SP1
12.0.6425.1000 KB953195 Office 2007 SP2
12.0.6607.1000 KB2526086 Office 2007 SP3

Office 2003

Build Number (MSO) KB Description
11.0.5614.0   Office 2003 RTM
11.0.6361.0 KB842532 Office 2003 SP1
11.0.7969.0 KB887616 Office 2003 SP2
11.0.8173.0 KB923618 Office 2003 SP3

Exchange Server build numbers

  RTM SP1 SP2 SP3 SP4 SP5
Exchange Server 2016 15.01.0225.042          
Exchange Server 2013 15.00.0516.032 15.00.0847.032        
Exchange Server 2010 14.00.0639.021 14.01.218.15 14.02.247.05 14.03.123.04    
Exchange Server 2007 8.0.685.25 8.1.240.6 8.2.176.2 8.3.083.6    
Exchange Server 2003 6.5.6944233 6.5.7226 6.5.7638      
Exchange Server 5.5 5.5.1960 5.5.2232 5.5.2448 5.5.2650 5.5.2653  
Exchange Server 5.0 5.0.1460 5.0.1458 5.0.1457      
Exchange Server 4.0 4.0.837 4.0.838 4.0.993 4.0.994 4.0.995 4.0.996

2016/12/09 06:05 2016/12/09 06:05
Posted
Filed under Study
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
(use regedit.exe or regedt32.exe to modify the registry)
  • wmic product (which only shows installed software through msiexec, fast but incomplete)
  • sc query type= driver (for installed drivers)
  • wmic qfe (for installed Windows updates)
  • How to uninstall software depends on where you found the program to uninstall. Respectively you should:

    • Use the UninstallString registry value as commandline
    • Use msiexec /x package.msi (More info)
    • Use pnputil -u -f drivername.inf (More info)
    • Use Wusa.exe patchname.msu

    사용자 삽입 이미지

    서버코어 모드에서는 UI지원이 한정되어 있어서 파워쉘이나 명령줄로 처리를 해야되는 경우가 종종 있습니다. 필자는 파워쉘은 커녕 명령어 조차도 제대로 외우지도 못하고 구글에 검색하기만 했었는데 서버코어에 올라간 어플리케이션이나 에이젼트를 삭제할때는 레지스트리를 삭제하는게 아니고 명령줄을 복사해서 커맨드에 붙여넣고 실행하면 바로 언인스톨을 진행합니다.

2016/11/05 18:19 2016/11/05 18:19
Posted
Filed under Study
윤지네 홈쇼핑 있었을때였습니다. RAC 오라클 서버였는데 언제부터인가 오라클이 차지하는 메모리를 제외하고 점점 메모리 사용율이 높아져만 갔었습니다. 작업관리자를 열어봐도 오라클 이외에 딱히 쓰는게 보이지가 않았던? 희안한 증상이였죠.
사용자 삽입 이미지

그럼 커널쪽에서 뭔가 먹고 있나 싶었습니다.
 위 그림으로만 봤을때는 딱히 문제시 될만한 프로세스가 없습니다. 그냥 정상처럼 보일뿐입니다.
사용자 삽입 이미지

그런데 실제 사용 메모리는 거의 끝까지 사용하고 있다는겁니다. 뭐 친절하게도 커널에 넌페이지 메모리가 보통 이상을 잡아먹는것이 보입니다. 흠 그럼 커널에서 누수를 일으키고 있는게 확실하단 말이네? 좋았어 그럼 이 범인을 반드시 잡아주마 하고 poolmon을 실행시켰습니다.
사용자 삽입 이미지
바이트로 정렬했더니 Proc 와 Thre 즉 프로세스와 쓰레드가 많은 메모리를 먹고 있다는걸 보여주고 있습니다. 지금까지 커널메모리 누수는 sys 같은 커널에 상주하고 있는 드라이버나 백신같은것들이 대부분이였는데 이증상은 의외였습니다. 한번도 경험해보지 않은 특이케이스중 X-File 같은 증상이였습니다. 이때까지만 해도 저 프로세스와 쓰레드가 정확히 무었인지 밝혀내지 못한 단계였기 때문에 추측으로 메모리 누수가 발생했던 시점을 유추해서 그당시 프로그램 설치했던 상황으로 용의자를 뽑았습니다. 딱 하나가 걸렸습니다. DB 모니터링을 하는 맥스게이지가 그당시 에이젼트를 설치했던 날이였습니다. 하지만 맥스게이지는 아무런 죄가 없는 프로그램이였습니다. 정황상 맥스게이지가 그 시점과 거이 동일했기 때문에 당신네 프로그램 때문에 지금 난리가 났다고 당장 직원보내라고 협박성 덤탱이를 씌웠던 그런날이 있었고 그 죄없는 어린직원은 얼굴이 잔뜩 겁먹고 온 상태여서 딱히 니탓내탓할 그런 액션을 취하지 않았습니다. 그런데 혹시나 싶어서 내가 헛다리 짚었으면 어뜩하지?라는 불안감에 다시 제대로 분석해보기로 했습니다. 실제 커널의 메모리 상태를 확인하기 위해서는 윈도우는 디버깅 모드를 활성화 시켜야 됩니다. 기본값은 보호를 위해 비활성 되었습니다.
bcdedit /debug on
위명령어로 디버깅 모드를 진행할수 있습니다. 그리고 재부팅후에 다시 증상이 발생했을때 WinDBG 유틸을 이용하여 커널디버그 모드를 들어갑니다.
!vm 명령을 사용하면 커널에 사용되는 메모리 정보가 주르륵 나옵니다
사용자 삽입 이미지

왠걸? 정말로 범인이 밝혀졌습니다. 역시나 poolmon에서 출력해서 보여줬던 결과처럼 프로세스가 무수히 많이 점유하고 있었던 것이였습니다. 이게 또 0kb 용량으로 점유하고 있었기 때문에 프로세스명이 메모리를 차지하고 있다고 출력을 못해주고 객체의 갯수만 많이차지하여 누수를 발생한 현상이였고 이 결과값이 출력되자마자 죄없는 맥스게이지는 누명을 벗게되는 그런날이 있었습니다. 하필 왜 그때 프로그램 설치해가지고...ㅋㅋㅋ
그럼 저 프로세스가 뭐냐면 파로스라는 DB모니터링 프로그램입니다.
사용자 삽입 이미지

그럼 왜 저증상을 불러일으켰냐면 저 문제를 불러일으킬 시점에 라이센스가 만료가 되었습니다. 만료가 되었으면 서비스를 중지를 하던가 삭제를 하던가 해야되는데 그런 통보를 전달해주지 않았기에 그냥 살려둔체로 메모리 누스를 일으켰던 분석하기도 정말 희안했던 케이스중 하나였습니다.
사용자 삽입 이미지

정상적인 커널메모리였을때는 위그림과 같이 넌페이지 커널메모리가 정상적인 값을 보여주고 있습니다.
대부분의 커널메모리 누수는 커널에 상주하는 드라이버,  그리고 백신 필터드라이버 나머지는 운영체제의 핵심들입니다. 운영체제는 특별히 버그이슈나 커널이슈가 존재하지 않는한 거이 메모리 누수가 발생하지 않습니다.(이제까지 그런 문제는 못봤습니다) 벤더사의 초기 드라이버들이 문제를 일으키는 케이스가 흔했었고 두번째로 멀쩡한 드라이버 핸들링하고 놔주지 않는 백신들이 두번째로 치명적인 문제를 보여줬었습니다. 리부팅하면 그런증상이 없어졌기 때문에 대부분의 엔지니어들은 윈도우가 원래 이렇다?리눅스 유닉스는 안그런데 윈도우랑은 호환성이 안맞는다?라고 도피성 결론을 내리고 덮어두는게 대부분입니다.
커널을 사용하지 않는 프로그램들은 유저모드에서 전부 모니터링이 되기때문에 누수에 대한건 금방 분석하고 결과를 유추할수 있습니다.
2016/07/07 02:29 2016/07/07 02:29