From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42550) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YVBO1-0002Qn-9L for qemu-devel@nongnu.org; Tue, 10 Mar 2015 00:03:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YVBNx-0002ez-3Y for qemu-devel@nongnu.org; Tue, 10 Mar 2015 00:03:17 -0400 Received: from isrv.corpit.ru ([86.62.121.231]:59791) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YVBNw-0002dj-SQ for qemu-devel@nongnu.org; Tue, 10 Mar 2015 00:03:13 -0400 Message-ID: <54FE6CF8.5080201@msgid.tls.msk.ru> Date: Tue, 10 Mar 2015 07:03:04 +0300 From: Michael Tokarev MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qemu-system return value when terminating due to a signal List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel When qemu is terminated by a signal, such as SIGINT (Ctrl+C), it exits with a zero, successful status. Is it intentional? Sure, from the qemu perspective, pulling the plug from the guest machine is a success. But maybe it's better to indicate that the exit was due to interrupt, not because of `exit' command which is a much better version of pulling the plug? If yes, what exit code should it return? Thanks, /mjt