On 07/25/11 06:10, Ross Finlayson wrote:
No, SO_REUSEADDR (and SO_REUSEPORT) is turned off for the server for a
very simple reason: We can't have more than one server on the same host
using the same port at the same time!
On Linux you can't bind twice even with SO_REUSEADDR, so it might make
s
Thanks for your reply. I agree that SO_LINGER is not the recommended
way of getting
round the TIME_WAIT state. I had a closer look at the RTSP server
code and realized that
the SO_REUSEADDR option is turned off at the server socket in
RTSPServer::setUpOurSocket()
and that is why the server cann
Hi Ross,
Thanks for your reply. I agree that SO_LINGER is not the recommended way
of getting
round the TIME_WAIT state. I had a closer look at the RTSP server code
and realized that
the SO_REUSEADDR option is turned off at the server socket in
RTSPServer::setUpOurSocket()
and that is why the
I run the 'testH264VideoStreamer' app and view the video with an
RTSP client (eg VLC).
If I kill 'testH264VideoStreamer' while the client is connected and
then try to run it again
straight away I get the following error:
Failed to create RTSP server: bind() error (port number: 8554):
Addr
Hi,
I run the 'testH264VideoStreamer' app and view the video with an RTSP
client (eg VLC).
If I kill 'testH264VideoStreamer' while the client is connected and then
try to run it again
straight away I get the following error:
Failed to create RTSP server: bind() error (port number: 85
