Since resources on a host are finite, it can be useful to know the
impact of a process or processes on those resources. In this instance,
we'll take a look at a process' use of memory. Our details for this are:
Showing posts with label processes. Show all posts
Showing posts with label processes. Show all posts
24 July 2011
17 February 2011
Network Ports and Processes (Windows)
Previously, I wrote up how to match open network ports to running
processes for FreeBSD, Solaris, and Linux. If UNIX hosts can correlate
ports to processes, shouldn't Windows Server be able to as well?
Beginning with Windows 2000, it can. Our host details for this are:
processes for FreeBSD, Solaris, and Linux. If UNIX hosts can correlate
ports to processes, shouldn't Windows Server be able to as well?
Beginning with Windows 2000, it can. Our host details for this are:
18 October 2010
Process Environments
When working on a host, it is sometimes of value to know the environmental
settings, such as PATH, that a process is currently using. Fortunately,
there a way of obtaining this information for Solaris, Linux, and FreeBSD.
The following is an example for cron from a Solaris x86 box (though sparc
settings, such as PATH, that a process is currently using. Fortunately,
there a way of obtaining this information for Solaris, Linux, and FreeBSD.
The following is an example for cron from a Solaris x86 box (though sparc
Network Ports and Processes
Looking at a host, there are times when it may be indeterminable
what process may be holding a particular port open. Perhaps because
there is no entry for the port in /etc/services, thus netstat, etc,
will not display a recognizable name. The reason may be that the port
what process may be holding a particular port open. Perhaps because
there is no entry for the port in /etc/services, thus netstat, etc,
will not display a recognizable name. The reason may be that the port
Subscribe to:
Posts (Atom)