Anand Kumria <[EMAIL PROTECTED]> writes: > On Fri, Jul 15, 2005 at 01:56:14AM +0200, Hans Ulrich Niedermann wrote: >> Package: zeroconf >> Version: 0.6-1 >> Severity: wishlist >> >> >> It would be very nice if one could add a DISABLE_ZEROCONF=yes switch >> or something similar to /etc/default/zeroconf. > > Why would you disable it completely? Why not just blacklist the > particular interface you are having problems with?
There are multiple valid reasons for disabling something completely: 1. I want to keep it installed in case I may need it some time, but do not need and thus do not want it active in everyday use. That is my typical laptop use case. 2. If a problem occurs during the "ifup -a" on boot, there is no running system in which one could easily check which of the interfaces is actually having the problem. Completely disable zeroconf it from a rescue system, boot up, and then check each interface from the running system is much easier than finding out what all the possible interfaces could be called like. If you do a reasonable amount of tunneling, it is not easy to keep track of all that tun* and tap* device numbers which you have to explictly disable. >> This could come in quite handy in cases where something goes wrong >> with zeroconf. Oh right, and here is reason #3: 3. There may be something wrong with zeroconf, and I may want to start my system and help debugging the zeroconf problems. But if the only way to disable zeroconf and boot the system is to "dpkg --purge" zeroconf, the very thing I'm helping debug is removed along with all the things I possibly tried to fix it. Bummer. :) >> I've just experienced a case of a system hanging indefinitely at >> "ifup -a" time while booting, which was caused by this old > > I'm aware of why that occurs and I hope to have that fixed in zeroconf > 0.7 Ah good. >> /etc/network/if-up.d/zeroconf script: >> >> ,---- >> |#!/bin/sh >> | >> |/usr/sbin/zeroconf -i $IFACE >> `---- >> >> which probably some older package had left lying around. >> >> Having no clean way to disable zeroconf, I resorted to >> "dpkg --purge zeroconf", which then, incidentally, didn't remove the >> /etc/network/if-up.d/zeroconf script. But that was ok - at least >> "ifup -a" was failing now, not hanging. > > Hmm - okay, so for the 'upgrade' from zeroconf 0.3 to zeroconf 0.6 since > it was only in testing, I just modified the names of the files rather > than doing a 'clean' upgrade. Hmm... if I have to manually clean something up, then I definitely miss the place where README.Debian or the message on package installation says "if you've just upgraded from 0.3, you have to clean up files manually". :) > I would recommend you 'dpkg -P zeroconf' and ensure that no trace of the > if-up script remains in /etc/network/if-up.d/; then re-install it. That's effectively what I've done. >> Hmm... perhaps "ifup -a" should use a timeout, but that would be >> a seperate wishlist bug, I think. > > Interesting idea - definitely worth putting a bugreport on. Done; waiting for bug number. Uli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
