On Wed, Mar 13, 2013 at 04:33:34PM -0600, Eric Blake wrote:
> On 03/13/2013 11:24 AM, Daniel P. Berrange wrote:
> > From: "Daniel P. Berrange"
> >
> > When opening a stream to a device which is a TTY, that device
> > may become the controlling TTY of libvirtd, if libvirtd was
> > daemonized. This
On 03/13/2013 11:24 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> When opening a stream to a device which is a TTY, that device
> may become the controlling TTY of libvirtd, if libvirtd was
> daemonized. This in turn means when the other end of the stream
> closes, libvirtd gets
From: "Daniel P. Berrange"
When opening a stream to a device which is a TTY, that device
may become the controlling TTY of libvirtd, if libvirtd was
daemonized. This in turn means when the other end of the stream
closes, libvirtd gets SIGHUP, causing it to reload its config.
Prevent this by forci