Hi Jan,
Jan Stary wrote:
[ skipped ]
*Usually* (I know) it finishes OK, and the *ogg is a valid ogg stream.
In this failing case, it *also* is a valid ogg stream, but much
shorter than usual.
So I suppose the background nc dies before I try to kill it myself
(that is, after sleeping for $LENGTH seconds).
One reason for this to happen is that the ogg being streamed out just
finishes before $LENGTH (a special case being it returns immediately,
possibly getting a HTTP error and an immediate EOF. But I doubt that
- it's a continuously streamed radio station). Or the running nc(1)
loses connection?
Or maybe the inner structure of live-streamed OGG's is such that the
(in fact) HTTP response is EOFed when one show finishes and another
starts?
Or, obviously, my script is somehow wrong - any hints?
Sorry if this is trivial.
Thanks for your time
Jan
Since only happens infrequently, I'd start 'nc' under trace, and
preserve the trace file in the case when 'kill' has nothing to kill.
Trace file should show what 'nc' encountered on the network...
