SOA in Cardiac Arrest, Long Live Services


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News SOA in Cardiac Arrest, Long Live Services
# 1  
Old 01-11-2009
SOA in Cardiac Arrest, Long Live Services

Tim Bass
01-11-2009 01:01 PM


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Long Delay if any with network services

While installing a firewall, I was pinging the interface from SCO 5.0.6 Openserver box, while no response, I hit "DEL" to cancel, but no cancel. Then all of a sudden I get BOO-KOO traffic lights on HUB and Switch.... Then a kernel trap error. System froze... Proceeded with a cold boot. Now I have... (8 Replies)
Discussion started by: nashvillek5
8 Replies
Login or Register to Ask a Question
PORTRESERVE(1)						   TCP port reservation utility 					    PORTRESERVE(1)

NAME
portreserve - reserve ports to prevent portmap mapping them SYNOPSIS
portreserve DESCRIPTION
The portreserve program aims to help services with well-known ports that lie in the bindresvport range. It prevents portmap (or other programs using bindresvport) from occupying a real service's port by occupying it itself, until the real service tells it to release the port (generally in its init script). It is intended that portreserve runs from an initscript of its own, and services wishing to interact with it should use portrelease. 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. FILES
/etc/portreserve/* Service configuration files /var/run/portreserve/socket communication socket for portrelease SEE ALSO
portrelease(1) AUTHOR
Tim Waugh <twaugh@redhat.com> Author. portreserve 1 July 2008 PORTRESERVE(1)