Package: ifupdown Version: 0.6.4-4.12 Severity: normal In cases when the script specified in a mapping stanza of /etc/network/interfaces does not read from stdin (I mean, at all. Not a single byte), ifup dies from SIGPIPE, without any diadnostic messages or indication of the reason. I had to use strace to find this out. In fact, it's a rather realistic example to have a mapping script that doesn't read its stdin -- it can be just a simple one-liner that says 'HOME' or 'OFFICE' basing on some condition, without actually analyzing the alternatives that ifup offers it.
I think that ignoring SIGPIPE would be better. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-1-686 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages ifupdown depends on: ii debconf [debconf-2.0] 1.4.30.13 Debian configuration management sy ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii net-tools 1.60-10 The NET-3 networking toolkit -- debconf information: ifupdown/convert-interfaces: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
