Charles Arnold wrote:
>> 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,
This is probably the case. xenstored.service must be running before
xencommons.service. Since xencommons will start xenstored, we may not
need xenstored.service right?
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
