From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51498) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLbvv-0005Ci-Ux for qemu-devel@nongnu.org; Thu, 06 Mar 2014 12:18:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WLbvo-00041J-Le for qemu-devel@nongnu.org; Thu, 06 Mar 2014 12:18:11 -0500 Received: from mail-oa0-f41.google.com ([209.85.219.41]:33809) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLbvo-000414-H1 for qemu-devel@nongnu.org; Thu, 06 Mar 2014 12:18:04 -0500 Received: by mail-oa0-f41.google.com with SMTP id j17so2905637oag.14 for ; Thu, 06 Mar 2014 09:18:03 -0800 (PST) Message-ID: <5318ADC8.1060708@mvista.com> Date: Thu, 06 Mar 2014 11:18:00 -0600 From: Corey Minyard MIME-Version: 1.0 References: <1393979937-9082-1-git-send-email-minyard@acm.org> <1393979937-9082-3-git-send-email-minyard@acm.org> <53181A10.6070203@huawei.com> In-Reply-To: <53181A10.6070203@huawei.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/7] qemu-char: Allow a chardev to reconnect if disconnected List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Weidong Huang , minyard@acm.org Cc: bcketchum@gmail.com, qemu-devel@nongnu.org, afaerber@suse.de, mst@redhat.com 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