• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

Linux OS Service ‘portreserve’

by admin

The portreserve program aims to help services with well-known ports that lie in the portmap range. It prevents portmap from a real service’s port by occupying it itself, until the real service tells it to release the port (generally in the init script).

For example the cups package provides /etc/portreserve/cups.

# cat /etc/portreserve/cups 
ipp

In /etc/services, it is defined “service-name ipp” is equal to 631 ports. When portreserve service starts, portreserve reserves 631 ports.

# cat /etc/services | grep -w ipp
ipp             631/tcp                         # Internet Printing Protocol
ipp             631/udp                         # Internet Printing Protocol
# netstat -lanp | grep 631
udp        0      0 0.0.0.0:631                 0.0.0.0:*                               1628/portreserve

Configuration Files

– /etc/portreserve/* – Service configuration files
– /var/run/portreserve/socket – communication socket for portrelease

What happens when portrelease daemon starts

When the portreserve daemon is started, it examines the /etc/portreserve/ directory. Each file not containing “.” or “~” in its name is considered to be a service configuration file, and must contain a service name (as listed in /etc/services) or a port number. UDP services may be specified by appending “/udp” to the service name, and TCP services by “/tcp“. Several services may be specified, one per line.

For example, /etc/portreserve/cups might contain the string “ipp” or, equivalently, “ipp/tcp” and “ipp/udp” on separate lines.

For each service configuration file, a socket is created and bound to the appropriate port. A service wishing to bind to its port must first run portrelease, which instructs portreserve to release the port associated with the service.

Once all the reserved ports have been released, the daemon exits.

Filed Under: Linux, Linux Services

Some more articles you might also be interested in …

  1. grub-install Command Examples in Linux
  2. Beginners Guide to NFS in CentOS / RHEL
  3. isoinfo: command not found
  4. i3: command not found
  5. How to Disable NetworkManager in CentOS/RHEL 8
  6. gpasswd: command not found
  7. How to Set Environment Variables for a systemd Service in CentOS/RHEL 7
  8. flatpak Command Examples in Linux
  9. CentOS / RHEL : How to Recover from deleted /etc/passwd file
  10. test: command not found

You May Also Like

Primary Sidebar

Recent Posts

  • nixos-rebuild Command Examples in Linux
  • nixos-option: Command Examples in Linux
  • nixos-container : Command Examples in Linux
  • nitrogen Command Examples in Linux

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright