On Thu, Mar 06, 2014 at 11:18:00AM -0600, Corey Minyard wrote:
> On 03/06/2014 12:47 AM, Weidong Huang wrote:
> > escape sequences.
> >
> > +@option{reconnect} specifies that if the client socket does not connect at
> > +startup, or if the client socket is closed for some reason (like the other
> > +end exited), wait the given number of seconds and attempt to reconnect.
> > +
> > TCP and unix socket options are given below:
> >
> > @table @option
> > The client will reconnect for ever when the server is dead. Is it better
> > that try to reconnect several times?
> > Or add a option which specifies times of reconnect?
> >
> I'm not really sure about this. For a remote IPMI BMC, you would want
> it to reconnect for forever, there's no point it having it stop trying
> after a while, since you want it to come back even if the BMC is down
> for a day. I would think the same if you wanted a remote console or
> something of that nature.
>
> What's the use case where you would want it to stop trying? I can't
> think of any.
>
> Thanks,
>
> -corey
Depends on what happens after it fails.
Imagine whoever was using the socket is gone.
It might be useful to stop VM or exit
after a while rather than just hang about.
--
MST
