ia64/xen-unstable

changeset 8010:8aabf8959595

Don't treat the failure of ifconfig vifX.Y down as a fatal error. This hasn't
emerged as a problem in the field, AFAIK, but it seems that distro scripts
could have brought the device down already by this point (Debian stable's
net.agent does ifdown vifX.Y, and it wouldn't surprise me if someone decided
to do ifconfig vifX.Y down if this failed, for example).

Logging but ignoring the failure seems sensible.

Signed-off-by: Ewan Mellor <ewan@xensource.com>
author emellor@leeni.uk.xensource.com
date Wed Nov 23 19:16:54 2005 +0000 (2005-11-23)
parents e48bb8550f95
children d6034e0e95fc
files tools/examples/vif-bridge
line diff
     1.1 --- a/tools/examples/vif-bridge	Wed Nov 23 19:13:13 2005 +0000
     1.2 +++ b/tools/examples/vif-bridge	Wed Nov 23 19:16:54 2005 +0000
     1.3 @@ -62,7 +62,7 @@ case "$command" in
     1.4  
     1.5      offline)
     1.6          # vifs are auto-removed from bridge.
     1.7 -        ifconfig "$vif" down || fatal "ifconfig $vif down failed"
     1.8 +        ifconfig "$vif" down || log err "ifconfig $vif down failed"
     1.9          ;;
    1.10  esac
    1.11