Re: ifup/ifdown are not idempotent

[wpmills@Mills-USA.com (W. Paul Mills)]

madduck@madduck.net (martin f krafft) writes:

> [1  <text/plain; iso-8859-15 (quoted-printable)>]
> check this series of commands:
>
> fishbowl:~> sudo ifconfig eth0
> eth0      Link encap:Ethernet  HWaddr 00:20:78:10:82:FD  
>           inet addr:130.60.48.193  Bcast:130.60.255.255  Mask:255.255.255.0
>           inet6 addr: fe80::220:78ff:fe10:82fd/10 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:192 errors:0 dropped:0 overruns:1 frame:0
>           TX packets:1287 errors:0 dropped:0 overruns:0 carrier:1276
>           collisions:0 txqueuelen:100 
>           RX bytes:18419 (17.9 KiB)  TX bytes:77454 (75.6 KiB)
>           Interrupt:11 Base address:0xec80 
>
> fishbowl:~> sudo ifdown eth0
> SIOCDELRT: No such process
>
> fishbowl:~> sudo ifup eth0
> SIOCSIFHWADDR: Device or resource busy
>
> fishbowl:~> sudo ifconfig eth0 down
>
> fishbowl:~> sudo ifup eth0
> ifup: interface eth0 already configured
>
> fishbowl:~> sudo ifdown eth0
> SIOCDELRT: No such process
>
> fishbowl:~> sudo ifup eth0
>
> finally... if you ask me, this shouldn't be. has anyone else
> experienced this?

You are mixing apples and oranges. Or I suspect this is because
ifup/down stores state information in /etc/network/ifstate. 
Ifconfig does not.

Paul





-- 
*  For God so loved the world that He gave his only begotten Son,  *
*  that whoever believes in Him should not perish...    John 3:16  *