Back to Blog
How to open a patch with dup26/13/2023 I.e., due > to daemon(3) interface being unflexible/unsuitable for the > current use case. Second > fork (to the one which is already done in daemon(3)) has > been done to work around lack of proper communication between > parent and child in case of using plain daemon(3). > Is it good or bad? There's no need to fork twice. > if (pid = 0) > This is forking only once. X-detected-operating-system: by : GNU/Linux 2.6 (newer, 2)Ĭc: Paolo Bonzini, rework daemonizing logic in qemu-nbdĮrrors-To: Bonzini Jan. Received: by (Postfix, from userid 1000) Received: from (.ru )īy (Postfix) with ESMTP id 8010DA081B ![]() Received: from Debian-exim by with spam-scanned (Exim 4.71) Received: from localhost (:56293 helo=)īy with esmtp (Exim 4.71) (envelope-from (using TLSv1 with cipher AES256-SHA (256/256 bits))īy (Postfix) with ESMTPS id B85C3B6EFF
0 Comments
Read More
Leave a Reply. |