I have been living and working in Australia since 1st day of last month. The creativity and energy of my local colleagues have always broadened my horizons. A friend from there took me and my wife out for dinner a few days ago. He said the restaurant is only a few steps away from our hotel.
Forty minutes later, we arrived at a very beautiful restaurant with a view of Sydney Harbor, the Sydney Opera House shining brightly like a shell embedded in a colorful beach. The longest single cross-bridge in the world) The harbour bridge opens a strong arm to hold the peninsula on both sides.
A 40-minute walk is not a short stroll. It is a routine exercise that requires 15 minutes of warm-up and stretching.
One of the reasons why I like this trip to Australia is that my colleagues there have different perspectives on the issue. Their methods seem ingenious, often contrary to my conventional logic.
In the field of scripting, it is easy to stick to the rules if you stick to the "tried and correct" method in your mind. Most of the time, what you really want to see is to use the same method to get the same results.
Taking monitoring as an example, by using Windows PowerShell, you can easily obtain excellent snapshots of process usage on the local computer. With the Get-Process cmdlet, you will Get a clear output, as shown in 1.
Figure 1 use Get-Process to view local processes
The results of the Get-Process cmdlet are useful in most cases. They display the number of opened handles, various memory usage views, and CPU usage snapshots. After Windows PowerShell 2.0 is launched, you can even use the Get-Process and-computername parameters to retrieve this overview from a remote computer. Since there are these benefits, why does someone bother researching other products?
The problem is that a large amount of details are hidden behind lengthy data. Data often hides more important details. Although Windows PowerShell 2.0 will support the-computername parameter in the future, it is still a mirage for network administrators. Therefore, we have to use the Windows Management Specification (WMI) and Win32_Process WMI classes to monitor remote systems and display information in a practical way. If you think that the Get-Process output is rich, take a closer look at Win32_Process output 2 ).
Figure 2 view Processes Using WMI