[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-bugs
Subject:    [Xen-bugs] [Bug 1470] Not only status executes network-* start
From:       bugzilla-daemon () lists ! xensource ! com
Date:       2009-08-19 8:13:45
Message-ID: 200908190813.n7J8DjjE027211 () bugzilla ! xensource ! com
[Download RAW message or body]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1470


adamc@pons.pl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adamc@pons.pl
            Summary|xend status executes        |Not only status executes
                   |network-* start             |network-* start




------- Comment #1 from adamc@pons.pl  2009-08-19 01:13 -------
I've noticed something similar.
On debian lenny (5.0.2) with xen 3.2-1 (fresh installation) I've made my own
network-bridge script and observed that stopping xen hypervisor does not put
down interfaces as I wish. After some investigation, I've modified
network-dummy script (with "echo ${@}"), and I can see, when I invoke
~# /etc/init.d/xend stop
the message:
Stopping XEN control daemon: xendstart
start
.

The init script invokes /usr/lib/xen-$VERSION/bin/xend and if I invoke by hand 
~# python /usr/lib/xen-3.2-1/bin/xend stop
it shows:
start
~# python /usr/lib/xen-3.2-1/bin/xend anything
start
not an option: anything

So, anything I do, one of the xen scripts returns "start" (but which script?)


-- 
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[prev in list] [next in list] [prev in thread] [next in thread]