qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] stale pid files?
Date: Fri, 01 Jun 2007 08:47:13 -0500	[thread overview]
Message-ID: <46602361.3080503@codemonkey.ws> (raw)
In-Reply-To: <465FFAFF.50800@kittenberger.net>

Axel Kittenberger wrote:
> Hi list again, another suggestion.
>
> I use the deamons pidfile feature to write pidfiles so I can controll 
> the virtual machines with /etc/init.d/bla scripts, to e.g. auto spawn 
> the guests when the server starts, auto/start/stop with runlevels and 
> so on.. However I got following issue, the daemon wont start if there 
> is a pidfile already (yes no problem for user to delete, but for auto 
> spawning after unattended boot) . Since e.g. following situation: 
> BANG! Powerout! .... System goes up when power is available again. The 
> init scripts want to start the qemu/kvm deamons, but they refuse 
> because these see their pidfiles already from pre-powerout..

-pidfile behaves properly in CVS.  You may be able to find the patch on 
the ML that fixed it.

Regards,

Anthony Liguori

> I have seen other daemons somehow locking their pidfiles while 
> running, and when killed -9ed, or poweroutes and they start again, 
> they see their pid-file is unlocked, thus stale, and just overwrite 
> it... only notifing you with a message they did so.
>
> Kind Regards,
> Axel
>
>
>

      reply	other threads:[~2007-06-01 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 10:54 [Qemu-devel] stale pid files? Axel Kittenberger
2007-06-01 13:47 ` Anthony Liguori [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46602361.3080503@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).