Скачать или смотреть How to Easily List Processes Based on TCP Port in Linux

Learn how to create a bash function and alias that lists processes by their TCP port number in Linux, making it simple to monitor your server's activity.
---
This video is based on the question https://stackoverflow.com/q/73114535/ asked by the user 'Fernando Fabreti' ( https://stackoverflow.com/u/873650/ ) and on the answer https://stackoverflow.com/a/73114879/ provided by the user 'Fernando Fabreti' ( https://stackoverflow.com/u/873650/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: list process based on tcp port

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Easily List Processes Based on TCP Port in Linux

When managing a Linux server, it’s essential to keep track of processes running on specific TCP ports. Whether you're troubleshooting connectivity issues or checking for rogue applications, being able to list processes by their TCP port can save you time and frustration.

In this guide, we'll guide you through the steps to create a bash function and alias that will let you easily list processes based on TCP port.

Understanding the Problem

To list processes associated with a specific TCP port, you might typically use a command structure like:

[[See Video to Reveal this Text or Code Snippet]]

This command:

Uses fuser to identify which process is listening on TCP port 5432.

The output from fuser feeds into the ps command, which displays detailed information about those processes.

While this works, typing these commands every time can be cumbersome. You might think about creating an alias, but as you found out, a simple alias won’t work due to the restrictions of passing parameters directly.

The Solution

Step 1: Create a Function

The solution lies in creating a bash function that can handle the input parameters while also coping with the error output emitted by fuser. Here’s how you can define the function:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Create an Alias

With the function in place, let's set up an alias that will mute any error messages from the fuser command, making the command more user-friendly:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Using Your New Alias

Now, you can use your new alias like this:

[[See Video to Reveal this Text or Code Snippet]]

This command will:

Check for processes running on both TCP ports 5432 and 5433.

Display the associated process IDs (PIDs) and their details.

Example of Output

When you run p2p 5432/tcp 5433/tcp, you will see output similar to:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By creating a simple bash function and alias, you can quickly list processes associated with specific TCP ports, improving your efficiency in server management.

Now that you have the tools at your disposal, consider implementing them into your workflow to streamline process monitoring.

Don’t forget, if you encounter errors, you can always modify your function and alias to meet specific needs or troubleshoot any issues that arise. Happy scripting!