Your message dated Mon, 16 Nov 2015 23:28:59 +0100
with message-id <[email protected]>
and subject line Please allow user cmds for "ifup A" to call "ifup B"
has caused the Debian Bug report #112992,
regarding Please allow user cmds for "ifup A" to call "ifup B"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
112992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=112992
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ifupdown
Version: 0.6.4-4.4
Severity: normal
When you use ifdown or ifup in the 'down' or 'up' stanzas of the interfaces
file,
you can cause what seems like a deadlock.
I was trying to do this:
iface eth0 inet static
address 192.168.0.22
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
up /sbin/ifup eth0:0
down /sbin/ifdown eth0:0
so that bringing up eth0 would also bring up eth0:0. Doing it this way causes
ifup (or ifdown) to hang. Using ifconfig instead makes everything work.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux laptop 2.4.19 #1 Mon Nov 18 20:06:17 CET 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages ifupdown depends on:
ii libc6 2.2.5-14.3 GNU C Library: Shared libraries
an
ii net-tools 1.60-4 The NET-3 networking toolkit
--- End Message ---
--- Begin Message ---
This has been possible for a long while.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
