From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55386) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RlzsT-0002Fs-7J for qemu-devel@nongnu.org; Sat, 14 Jan 2012 04:26:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RlzsS-000684-1e for qemu-devel@nongnu.org; Sat, 14 Jan 2012 04:26:21 -0500 Received: from isrv.corpit.ru ([86.62.121.231]:58944) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RlzsR-00067V-QL for qemu-devel@nongnu.org; Sat, 14 Jan 2012 04:26:20 -0500 Message-ID: <4F114A30.3070700@msgid.tls.msk.ru> Date: Sat, 14 Jan 2012 13:26:08 +0400 From: Michael Tokarev MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qemu-nbd daemonizing? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , qemu-devel After looking at the yesterdays issue with non-absolute paths for qemu-nbd arguments and daemon(3), I've a question. Why qemu-nbd daemonizes, and does that only when device argument is given (dropping -v/verbose case for now)? This raises two questions: - shouldn't it do the same daemonizing in case of usual tcp export? - shouldn't the daemonizing itself be controlled by an option (like -d), and why we can't just send it to background using "&" shell constuct? And while at it, I wonder why it is really unix-only? There's nothing unix-specific in there exept two things: it is the device handling (/dev/nbdX) and all the hacks around this (including this daemonizing). The rest should work on win32 just fine. Thanks, /mjt