> On Feb 20, 2019, at 7:53 AM, Kevin Bailey wrote:
>
> My particular use case has my program started and stopped rapidly in short
> periods of time. But I can't start and stop it like this if I can't quickly
> re-bind to the rtsp port. Maybe this doesn't have anything to do with my
> clean u
On Feb 19, 2019, at 11:53 AM, Kevin Bailey wrote:
>
> Maybe this doesn't have anything to do with my clean up code?
Indeed it doesn’t. The “problem” is that Live555 doesn’t set SO_REUSEADDR,
which it is technically correct to do:
https://stackoverflow.com/a/3233022/142454
You can set it
And I am also noticing now that netstat says that the rtsp port I am using
is in the following state "FIN_WAIT2". After I kill my client then it moves
to "TIME_WAIT". Which leads me to believe that the clean up code
listed in testProgs/testRTSPClient.cpp
does not sufficiently close the rtsp connect
My particular use case has my program started and stopped rapidly in short
periods of time. But I can't start and stop it like this if I can't quickly
re-bind to the rtsp port. Maybe this doesn't have anything to do with my
clean up code? Is it related to this:
https://live-devel.live555.narkive.co
In general, you can clean up by deleting things in the reverse order from which
they were created.
But why don’t you just call “exit()”? Why do you need to keep using the
process after you’ve gotten rid of the RTSP server?
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_
