Sockets bind to the same port in RHEL6.5 and later
Issue
- A Qt 4 Application which opens a listening socket can have another process bind and listen to the same port
- If a Qt4 application is listening to port 1234, another instance of the application can be launched to bind and listen to the same port
- The expected behaviour is that no two applications are supposed to listen to the same port
Environment
- Red Hat Enterprise Linux 6.5 and later
- Qt 4.6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.