[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: |
Corey Minyard |
Subject: |
Re: [Qemu-devel] [PATCH 2/7] qemu-char: Allow a chardev to reconnect if disconnected |
Date: |
Thu, 06 Mar 2014 11:18:00 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
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
[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