search for: try_xenstor

...in/$XENSTORED ;; '') USER_XENSTORED="" ;; esac ? > + # First, we check if any of xenstored or oxenstored is already running. If > + # so, we abort and leave it alone, even if the user has switched the value > + # in /etc/default/xen from one to another. > + for try_xenstored in "$OXENSTORED" "$CXENSTORED"; do > + if [ -x $try_xenstored ]; then > + start-stop-daemon --start --quiet --pidfile "$XENSTORED_PIDFILE" \ > + --exec "$try_xenstored" --test > /dev/null > + if [ $? -eq 1 ]; then > + return 1...

The contents are the wip.testme branch currently on salsa. I combined the wip.initscript and wip.oxenstored into this and added more things today. I think this is pretty gtg and it's smoke tested (in several cases by scping files around instead of doing package build), so it needs a final extra review and test round before putting it in master branch (which I don't want to force push). I

...xenstored_start > case "$?" in > 0|1) ;; > *) log_end_msg 1; exit ;; > esac > > I mean, why torture the reader of the code with counter intuitive 1 > values that mean success... I agree. Madness. > > for try_xenstored_var in $try_xenstoreds; do > > eval "try_xenstored=\$$try_xenstored_var" > > ... > > Yes, that way the two start-stop-daemon can be one instead, nice! > > And do you agree that exploding when an explicit choice has been made by > the user + that bina...