What Are Listeners?
Listeners are processes on your system that expose network ports, accepting incoming connections. When you run a web server, database, or any service that listens on a port, psys detects and displays it in the listeners table. psys uses the Linuxss (socket statistics) command to discover all listening TCP sockets on your system:
Listeners Table Columns
The listeners table displays comprehensive information about each listening process:Process
Shows the process name with an appropriate icon. psys automatically detects common services and displays recognizable icons for:- Node.js processes
- Next.js applications
- Redis servers
- MongoDB databases
- PostgreSQL databases
- MySQL/MariaDB databases
- Apache/httpd web servers
- SSH daemons
Docker Status
Indicates whether this port is published by a Docker container. When Docker publishes a container port to the host, psys shows the Docker icon and uses the container name as the service label.Port
The TCP port number the process is listening on.Address
The IP address the service is bound to. Common addresses include:0.0.0.0- Listening on all IPv4 interfaces127.0.0.1- Localhost only (IPv4)::,::1,[::1]- IPv6 addresses- Private network addresses (10.x, 192.168.x, 172.x)
Address Description
psys provides human-readable explanations of what each address means:The address
127.0.0.53 is typically used by systemd-resolved, the system DNS resolver on modern Linux distributions.Connections
Displays badge indicators for established connections from this listener to other services. Shows up to 5 connection targets with a “+N” badge if there are more.PID
The Process ID of the listening process. This is used for process management operations.Service Label Detection
psys automatically recognizes common services by their port numbers and provides helpful labels:How Detection Works
The detection logic follows this priority:- psys itself - Identifies if the listener is the psys app
- Docker containers - Uses
docker psto match ports to container names - Process name - Reads from
/proc/{pid}/comm - Known ports - Falls back to well-known port mappings
- Unknown - Shows “port (unknown)” if nothing matches