Package: ifupdown Version: 0.6.7 Severity: wishlist
I recently had a case of a /etc/netword/if-up.d/ script looping endlessly (bug #318350). This prevented my system from booting, because the "ifup -a" in /etc/init.d/networking never finished. So I considered that those hooked scripts may do just anything, and a single hook script running amok can completely halt your boot process. Thus I proposed to add a timeout for running hook scripts in the #318350 discussion, and Anand Kumria toldme to commit it here :) So, if an interface hasn't come up in, say, something between 15 and 150 seconds, odds are that it won't come up ever, so "ifup" could just abort configuring this interface and continue with the next one, or just abort. In any case, definitely terminating within a finite time would help a lot. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (900, 'stable'), (700, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11.10-swsusp2-ndim-2 Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages ifupdown depends on: ii debconf [debconf-2.0] 1.4.51 Debian configuration management sy ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii net-tools 1.60-13 The NET-3 networking toolkit ifupdown recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
