Icecast dev - Aug 2004 - Icecast source number problem, ices frozen after reconnect attemps failure (icecastkh13 iceskh48)

Hi,

On 2003.11.26 15:42 Karl Heyes wrote:
> The reconnectattempts value is from the CVS code, and can be a bit awkward
> in general.
> 
> ices can have multiple instances and in these mods can have multiple shout
> connections per instance.  I don't think terminating ices for just one
> shout
> connection is acceptable, I'm more inclined to drop the
reconnectattempts
> completely and treating it as indefinite. Use a value of -1 now for the
> same
> effect.
That would be a showstopper for me. I _need_ ices to terminate if it cannot 
connect successfully. This ought to be an option, IMHO.

Melanie
--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

On Wed, 2003-11-26 at 17:33, Melanie wrote:
> Hi,
> 
> On 2003.11.26 15:42 Karl Heyes wrote:
> > The reconnectattempts value is from the CVS code, and can be a bit
awkward
> > in general.
> > 
> > ices can have multiple instances and in these mods can have multiple
shout
> > connections per instance.  I don't think terminating ices for just
one
> > shout
> > connection is acceptable, I'm more inclined to drop the
reconnectattempts
> > completely and treating it as indefinite. Use a value of -1 now for
the
> > same
> > effect.
> 
> That would be a showstopper for me. I _need_ ices to terminate if it cannot
> connect successfully. This ought to be an option, IMHO.
That would sound like a poor solution, a connection to one of the
servers could die for various reasons, killing all connections would
seem an extreme action. 

If you're thinking of notification then that could be achieved without
shutting down ices. What sort of thing would you _need_ to do after ices
shut down?

<p>karl.

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

Hi,

On 2003.11.26 20:44 Karl Heyes wrote:
> > That would be a showstopper for me. I _need_ ices to terminate if it
> cannot
> > connect successfully. This ought to be an option, IMHO.
> 
> That would sound like a poor solution, a connection to one of the
> servers could die for various reasons, killing all connections would
> seem an extreme action.
> 
> If you're thinking of notification then that could be achieved without
> shutting down ices. What sort of thing would you _need_ to do after ices
> shut down?
In that particular case, ices is driven by a GUI. It only uses one 
instance. I just think that the option to terminate on disconnect is 
valuable. Many common cases will only have one instance feeding one mount. 
In that scenario, it makes sense to terminate ices.

Terminating raises SIGCHLD, which the app reacts on, giving visual feedback 
and optionally attempting to restart.

Melanie
--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

On 26 Nov 2003, Karl Heyes wrote:
> That would sound like a poor solution, a connection to one of the
> servers could die for various reasons, killing all connections would
> seem an extreme action.
Couldn't you just kill that stream instance, and then kill ices if no
stream instances are left alive?

Disclaimer: I am not a developer.

Geoff.

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.