[Xen-devel] [PATCH] properly daemonize vncviewer

["Charles Coffing" <ccoffing@xxxxxxxxxx>]

Hi,

Currently, vncviewer is spawned from xm, but it doesn't properly get
daemonized.  The attached patch makes vncviewer run completely separate
from xm.

There are various reasons it should be daemonized, but the particular
problem we hit was that YaST called "xm create" and waited on output on
stdout/stderr; xm then spawned vncviewer (which never closed its
inherited stdout and stderr); xm then would exit, but YaST still had
open file descriptors, and therefore waited forever.  It would be
possible to work around in YaST, but it seemed cleaner to daemonize
vncviewer.

We've been running with a variant of this patch (a variant because we
use tightvnc, which requires different arguments) for many months, and
it works well.

Please consider applying to xen-unstable.

Thanks.

Signed-off-by:  Charles Coffing <ccoffing@xxxxxxxxxx>

xen-daemonize-vncviewer.diff
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel