> > i'm staring at
> >
> > if ! `${BINDIR}/xenstore-read -s / >/dev/null 2>&1`
> >
> > what exactly is the intent here?
>
> It checks the status of xenstore to see if it is running by reading from
> the socket (-s). On failure, it executes the code to start xenstored.
> After loading xenstored it then hits a while loop checking for up to 30
> seconds to see if things were properly setup.
> The only failure points are if xenstored is already running, xenstored
> could not be found, or it times out.
Is there any reason, then, NOT to simply move
edit /etc/init.d/xenstored
fi
echo Setting domain 0 name...
- ${BINDIR}/xenstore-write "/local/domain/0/name"
"Domain-0"
+ # ${BINDIR}/xenstore-write "/local/domain/0/name"
"Domain-0"
fi
+ ${BINDIR}/xenstore-write "/local/domain/0/name"
"Domain-0"
echo Starting xenconsoled...
which appears to 'cure' the "(null)" name issue.
reboot
...
xl list
Name ID Mem
VCPUs State Time(s)
Domain-0 0 1241
4 r----- 42.2
test1 1 1024
2 -b---- 7.9
test2 2 1024
4 -b---- 28.3
xenstore-ls | grep "Domain-0"
name = "Domain-0"
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
