Bug 24391

Summary:	cannot kill amd after interface disappears
Product:	Base System	Reporter:	larse <larse>
Component:	bin	Assignee:	Martin Blapp <mbr>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.2-RELEASE
Hardware:	Any
OS:	Any

Description larse 2001-01-16 19:10:04 UTC

Killing amd after a network interface dissappears (e.g., due to
ejected PC card) fails. Kill -9 works (of course) but leaves the
mount map in such a state that amd cannot be restarted.

We found this when changing pccard_ether to automatically kill and
restart network services based on card insertions/ejections. Since amd
can't be killed once the card is out, this scheme can't be made to work.

Fix: 

Kill amd before ejecting pccard. Requires user interaction.
How-To-Repeat: start amd
eject pccard
kill amd
restart amd

Comment 1 Martin Blapp freebsd_committer

2004-05-13 09:05:19 UTC

Responsible Changed
From-To: freebsd-bugs->mbr

Take this PR.

Comment 2 Martin Blapp freebsd_committer

2004-05-13 09:05:38 UTC

State Changed
From-To: open->feedback

Hi, is this still a problem with newer freebsd releases ?

Comment 3 Lars Eggert 2005-07-26 12:31:17 UTC

Hi,

I cannot test whether the bug persists as I have no longer access to  
the equipment. OK to close this, IMO.

Lars
--
Lars Eggert                                     NEC Network Laboratories

Comment 4 Matteo Riondato freebsd_committer

2005-08-28 20:11:21 UTC

State Changed
From-To: feedback->closed

Closed as per submitter's request