Right ok. Not a bug so much as confusion on my understanding of the --help description. I only used the previous version for a few days before upgrading so apologies for the mistake. Can I request that a inital connection timeout be added? 3mins is a long time to wait for being able to continue :( Also I cannot kill the process while it is connecting using the kill command, ctrl +c etc. This is causing me a few headaches as I'm doing some scripting using rtmpdump where the output is used for other time dependent processes. Cheers, Tom -----Original Message----- From: rtmpdump-bounces@mplayerhq.hu [mailto:rtmpdump-bounces@mplayerhq.hu] On Behalf Of Howard Chu Sent: 15 November 2009 15:30 To: rtmpdump discussion and development Subject: Re: [rtmpdump] bug: RTMPDump v1.9 (as of 15/11/2009) connection timeout param ignored Tom Shaw wrote:

Hey,

It seems that the connection timeout is ignored. In fact even 120secs the default is not honoured. It takes 3 minutes and 10secs for the connection to time out regardless of the setting I use in my command line. This is the error message when it finally does.

Not sure why you're reporting this as a bug in 1.9, since the connect behavior hasn't changed relative to 1.6. The code has never set a timeout on connects, just on reading from an established connection. -- hyc _______________________________________________ rtmpdump mailing list rtmpdump@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/rtmpdump