From owner-freebsd-net Sun Feb 16 18:19:41 2003 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA85A37B401 for ; Sun, 16 Feb 2003 18:19:39 -0800 (PST) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BCF743F85 for ; Sun, 16 Feb 2003 18:19:38 -0800 (PST) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost (unknown [3ffe:501:100f:f::6]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 73F2415214; Mon, 17 Feb 2003 11:19:47 +0900 (JST) Date: Mon, 17 Feb 2003 11:19:39 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Brooks Davis Cc: Abdul Basit , net@FreeBSD.ORG, 6bone@mailman.isi.edu Subject: Re: pim6sd crash In-Reply-To: <20030216145145.A30301@Odin.AC.HMC.Edu> References: <20030216145145.A30301@Odin.AC.HMC.Edu> User-Agent: Wanderlust/2.6.1 (Upside Down) Emacs/21.2 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 20000228(IM140) Lines: 34 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Sun, 16 Feb 2003 14:51:45 -0800, >>>>> Brooks Davis said: >> > on freebsd 5.0-Release, pim6sd crashes if i execute >> > ifconfig gifX destroy if it is running in background, >> > i need to restart it manually. >> >> > pim6sd display 'check_vif_state' Device not configured >> > and exits. any workaround ? >> >> A workaround is not to destroy an interface when pim6sd is running on >> the interface. >> >> Note that this kind of trouble is not specific to pim6sd. Dynamic >> interface creation/deletion is a big architectural change to the >> traditional BSD kernel, and I bet there are many other applications >> affected by such an operation. > The user of the destroy command of ifconfig is expected to be paying > attention. This is the functionaly equivalent of yanking a NIC out > of its slot. It is the case that applications that can't handle this > are broken and need to be fixed becase you shouldn't count on any > interfaces staying around. (Just in case) I didn't intend to say create/destroy is the wrong approach and pim6sd doesn't need a fix. My point is that create/destroy is a big change that can affect many applications (including pim6sd) and that a "workaround" is not to use the operation for now. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message