search for: evalvariables

...tialized. The checklog() and logmsg() functions take care of logging at the requested loglevel (set in xen.conf). This is different from line 4; logmsg is a function that logs to the console, syslog, or a file (xen.conf). The sigerr(), fatal(), success(), xenstore_read_default(), findCommand() and evalVariables() functions are modified versions of the same functions in Xen''s xen-script-common.sh file. I added line 191-198 for debugging, rather than calling the actual commands they fake their execution and only add a log entry. That''s why they are commented out. The actual routine start...

...tialized. The checklog() and logmsg() functions take care of logging at the requested loglevel (set in xen.conf). This is different from line 4; logmsg is a function that logs to the console, syslog, or a file (xen.conf). The sigerr(), fatal(), success(), xenstore_read_default(), findCommand() and evalVariables() functions are modified versions of the same functions in Xen''s xen-script-common.sh file. I added line 191-198 for debugging, rather than calling the actual commands they fake their execution and only add a log entry. That''s why they are commented out. The actual routine start...

...-patched kernel doesn't have the string netloop in there anywhere) the script exits right there. The following patch fixes it: --- network-bridge.ORIG 2006-10-08 19:04:48.000000000 +0200 +++ network-bridge 2006-11-01 00:13:36.000000000 +0100 @@ -59,7 +59,7 @@ findCommand "$@" evalVariables "$@" -modprobe netloop > /dev/null 2>&1 +modprobe netloop > /dev/null 2>&1 || true vifnum=${vifnum:-$(ip route list | awk '/^default / { print $NF }' | sed 's/^[^0-9]*//')} vifnum=${vifnum:-0} Mike.

...twork-camp netdev=eth0 bridge=xenbr0') /etc/xen/scripts/network-camp is the following simple script: --------------- begin script ----------- #!/bin/bash dir=$(dirname "$0") . "$dir/xen-script-common.sh" . "$dir/xen-network-common.sh" findCommand "$@" evalVariables "$@" echo $command --------------- end script ----------- This minimal configuration shows it is called twice with command=start on "/etc/init.d/xen start". This is not a big problem as the default scripts are idempotent, but it does make writing custom scripts harder. It al...

...dresses, interfaces # #============================================================================ dir=$(dirname "$0") . "$dir/logging.sh" . "$dir/xen-script-common.sh" . "$dir/xen-network-common.sh" . "$dir/locking.sh" findCommand "$@" evalVariables "$@" netdev=${netdev:-eth0} bridge=${bridge:-ovs0} addr=`ip addr show dev ${netdev} | egrep ''^ *inet'' | sed -e ''s/ *inet //'' -e ''s/ .*//''` if [ -n "$addr" ]; then echo "Invalid device: ${netdev} is up and has a val...

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This patch series adds support for network buffering in the Remus codebase in libxl. Changes in V3: [1/5] Fix redundant checks in configure scripts (based on Ian Campbell''s suggestions) [2/5] Introduce locking in the script, during IFB setup. Add xenstore paths used by netbuf scripts to xenstore-paths.markdown [3/5] Hotplug scripts setup/teardown invocations are now