Wrong timeout behavior or output

Bug #1278595 reported by Karl-Philipp Richter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
New
Undecided
Unassigned

Bug Description

The following result of invokation of ifup is possible in Ubuntu 13.10 with ifupdown 0.7.44ubuntu3:
<code>
time sudo ifup bond1
Waiting for a slave to join bond1 (will timeout after 60s)
No slave joined bond1, continuing anyway

real 0m5.388s
user 0m0.042s
sys 0m0.269s
</pre>
Either the timeout specification of 60s is wrong or the program reads the wrong variable or *something* is very misleading and should be clearified (in the output of the program).
/etc/network/interfaces:
<code>
auto lo
iface lo inet loopback

iface eth0 inet manual
    bond-master bond1
    bond-primary eth1 eth0

iface eth1 inet manual
    bond-master bond1
    bond-primary eth1 eth0

iface bond1 inet manual
    address 192.168.3.100
    netmask 24
    bond-slaves eth0 eth1
    bond-mode 0
    bond-miimon 100
</code>

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.