All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Tony Jones <tony@immunix.com>
Cc: xen-devel@lists.sourceforge.net
Subject: (Patch Trivial] restart issues (was :Re: reboot issues and xm hangs {FC4])
Date: Wed, 02 Mar 2005 17:24:56 -0800	[thread overview]
Message-ID: <42266768.2010506@us.ibm.com> (raw)
In-Reply-To: <20050303004330.GA14930@immunix.com>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

Tony Jones wrote:

> Running 'init.d/xend restart', stops xend, waits, but fails to restart it.
> 
> Running 'init.d/xend start' gets things going again.

Similar issue but 'xend start' didn't work. On rebooting dom0,
didn't come up either. This is only tangential, but I think
it would help to have an unconditional remove of the lockfile
in init.d/xendomains. I think xend and xm are getting borked
during a shutdown of a domain, and I'm not sure the lockfile
gets cleared anywhere else - so upon reboot of dom0, domains
don't get automatically built. (Minor nit). I'm probably
missing something but I don't see the point of the xm return
check and conditional remove(?)..

thanks,
Nivedita




[-- Attachment #2: xendomain.patch --]
[-- Type: text/plain, Size: 326 bytes --]

--- xendomains	2005-02-27 20:37:44.000000000 -0800
+++ xendomains.new	2005-03-02 17:01:33.664928000 -0800
@@ -96,9 +96,10 @@
 
     xm shutdown --all --wait --halt
 
-    RETVAL=$?
+#    RETVAL=$?
 
-    [ $RETVAL -eq 0 ] && rm -f $LOCKFILE
+#    [ $RETVAL -eq 0 ] && rm -f $LOCKFILE
+    rm -f $LOCKFILE
 
     on_fn_exit
 }

      reply	other threads:[~2005-03-03  1:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03  0:43 reboot issues and xm hangs {FC4] Tony Jones
2005-03-03  1:24 ` Nivedita Singhvi [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=42266768.2010506@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=tony@immunix.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.