Am 10.01.2016 um 21:54 schrieb chovy:
Since the client is not able to reconnect, it seems that it may be possible that the very server PROCESS which invokes ffmpeg to start the stream needs to be restarted, not just ffmpeg - I am assuming the main server daemon is NOT ffmpeg. I'm using nginx to server the .ts and index.m3u8 files...I don't see why a restart of nginx would be required
why don't you just ask on the nginx list?when nginx is the client of the ffmpeg stream and the "final client" is connected to nginx it's still not a ffmpeg issue - ffmpeg is NOT responsible to graceful handle client issues
signature.asc
Description: OpenPGP digital signature
_______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
