-invirt-remote (0.3.2) unstable; urgency=low
-
- * Don't pass untrusted arguments to xm info.
- * Exit with a non-0 error code on the host if there's an error.
- * Always exec instead of fork&exec on the remctl server so that return
- codes get passed on.
-
- -- Evan Broder <broder@mit.edu> Sat, 31 Jan 2009 03:51:54 -0500
-
invirt-remote (0.3.1) unstable; urgency=low
* invirt.remote.bcast: provide stderr text when remctl fails
COMMAND=/usr/sbin/invirt-listvms
;;
info)
- exec /usr/sbin/xm info
+ COMMAND=/usr/sbin/xm
;;
vnccert)
COMMAND=/usr/bin/invirt-vnc-getcert
;;
esac
-exec "$COMMAND" "$SERVICE" "$@"
+$COMMAND "$SERVICE" "$@"
case "$TYPE/$SERVICE" in
web/listvms )
- exec invirt-remote-listvms "$@" ;;
+ invirt-remote-listvms "$@" ;;
web/vnccert )
- exec invirt-remote-vnccert "$@" ;;
+ invirt-remote-vnccert "$@" ;;
control/help )
- exec invirt-remctl-help ;;
+ invirt-remctl-help ;;
control/create|control/install )
- exec invirt-remote-create "$SERVICE" "$MACHINE" "$@" ;;
+ invirt-remote-create "$SERVICE" "$MACHINE" "$@" ;;
control/listhost|control/list-host )
- exec invirt-remote-listhost "$MACHINE" "$@" ;;
+ invirt-remote-listhost "$MACHINE" "$@" ;;
control/* )
# Everything but create must go where the VM is already running.
- exec invirt-remote-control "$MACHINE" "$SERVICE" "$@" ;;
+ invirt-remote-control "$MACHINE" "$SERVICE" "$@" ;;
* )
- exec remctl "$(invirt-getconf hosts.0.hostname)" remote "$TYPE" "$SERVICE" "$@" ;;
+ remctl "$(invirt-getconf hosts.0.hostname)" remote "$TYPE" "$SERVICE" "$@" ;;
esac