[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 2/7] qemu-char: Allow a chardev to reconnect if
From: |
Michael S. Tsirkin |
Subject: |
Re: [Qemu-devel] [PATCH 2/7] qemu-char: Allow a chardev to reconnect if disconnected |
Date: |
Thu, 6 Mar 2014 19:41:10 +0200 |
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.
> >
> > address@hidden 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
[Qemu-devel] [PATCH 3/7] qemu-char: Wait until socket connect to report connected, minyard, 2014/03/04
[Qemu-devel] [PATCH 4/7] qemu-char: remove free of chr from win_stdio_close, minyard, 2014/03/04
[Qemu-devel] [PATCH 5/7] qemu-char: Close fd at end of file, minyard, 2014/03/04
[Qemu-devel] [PATCH 6/7] qemu-char: Clean up error handling in qmp_chardev_add, minyard, 2014/03/04
[Qemu-devel] [PATCH 7/7] console: Don't use the console if NULL, minyard, 2014/03/04