From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH] xenconsole: Allow non-interactive use Date: Thu, 23 Jul 2015 09:48:50 +0100 Message-ID: <1437641330.19412.37.camel@citrix.com> References: <1437584888-9074-1-git-send-email-martin@lucina.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZICBS-0002rn-V2 for xen-devel@lists.xenproject.org; Thu, 23 Jul 2015 08:48:55 +0000 In-Reply-To: <1437584888-9074-1-git-send-email-martin@lucina.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Martin Lucina , xen-devel@lists.xenproject.org Cc: Ian Jackson , Wei Liu , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Wed, 2015-07-22 at 19:08 +0200, Martin Lucina wrote: > If xenconsole is run with stdin closed or redirected to /dev/null, > console_loop() will return immediately due to failure to read from > STDIN_FILENO. This patch tests if stdin and stdout are both connected > to > a TTY and, if not, xenconsole will not attempt to read from stdin or > modify stdout terminal attributes. > > Existing behaviour when xenconsole is run from a terminal does not > change. > > This allows for non-interactive use, eg. running "xl create -c" under > systemd or piping the output of "xl console" to another command. > > Signed-off-by: Martin Lucina > Cc: Ian Jackson > Cc: Stefano Stabellini > Cc: Ian Campbell > Cc: Wei Liu Acked-by: Ian Campbell WRT the 4.6 freeze I'm torn between calling this a feature or a bugfix. A pair of nits, which probably aren't worth acting on: > @@ -176,8 +177,13 @@ static int console_loop(int fd, struct xs_handle > *xs, char *pty_path) > fd_set fds; > > FD_ZERO(&fds); > - FD_SET(STDIN_FILENO, &fds); > - max_fd = STDIN_FILENO; > + if (interactive) { > + FD_SET(STDIN_FILENO, &fds); > + max_fd = STDIN_FILENO; > + } > + else { > + max_fd = -1; > + } Looking at the rest of the file and tools/console subtree it seems the prevailing coding style is: } else max_fd = -1; (i.e. } brace on the same line as the else and no {} for single statements after an else). But maybe it would be better to set max_fd = -1 on declaration and do the max dance here as with the following cases? Ian.