From owner-freebsd-questions Sat Jun 10 12:57:13 2000 Delivered-To: freebsd-questions@freebsd.org Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24]) by hub.freebsd.org (Postfix) with ESMTP id 4C1A337C154 for ; Sat, 10 Jun 2000 12:57:10 -0700 (PDT) (envelope-from cjc@earthlink.net) Received: from dialin-client.earthlink.net (pool0886.cvx21-bradley.dialup.earthlink.net [209.179.195.121]) by eagle.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id MAA01791; Sat, 10 Jun 2000 12:57:08 -0700 (PDT) Received: (from cjc@localhost) by dialin-client.earthlink.net (8.9.3/8.9.3) id MAA01388; Sat, 10 Jun 2000 12:55:46 -0700 (PDT) Date: Sat, 10 Jun 2000 12:55:45 -0700 From: "Crist J. Clark" To: Xavier Lumine Cc: freebsd-questions@FreeBSD.ORG Subject: Re: bug report with malfunctioning KILL of cvsup process Message-ID: <20000610125545.C1197@dialin-client.earthlink.net> Reply-To: cjclark@alum.mit.edu References: <20000610124323.42179.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000610124323.42179.qmail@hotmail.com>; from dmyshkin@hotmail.com on Sat, Jun 10, 2000 at 08:43:23AM -0400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 10, 2000 at 08:43:23AM -0400, Xavier Lumine wrote: > To whom it may concern: > > I recently ran cvsup from XFree86 3.3.6, and was puzzled to find that > hitting STOP didn't work... furthermore, force closing it didn't work either > by clicking the close box... > OK. I try killall cvsup (i had three of the little beasts that refused to > die and i just relaunched...). nope. kill -TERM pid. nope. > kill -9 pid. nope. kill -TERM 1 and go into single user mode... then kill -9 > pid. nope. kill -FPE pid. nope. kill -CONT pid then kill -KILL pid. nope. > Tried ifconfig del'ing my network interface... still no. > > from what i was told on #FreeBSDhelp on EFNet, this is cause to send in a > bug report. Sent it to the wrong place if it is really meant to be a bug report, see 'man send-pr'. But anyway, no bug here. > the system version I was running is 4.0-RELEASE... GENERIC kernel... right > off the 4.0 CD. ps aux reports: > > root 2012 0.0 6.4 8804 8080 p2- D 7:05PM 0:51.09 cvsup > stable-supfile > root 2295 0.0 5.5 7836 6996 p2- D 12:31AM 0:01.62 cvsup > stable-supfile > root 2359 0.0 5.5 7900 6928 p2- D 1:26AM 0:01.58 cvsup > stable-supfile Were you writing to an NFS mount or having disk trouble? Look at the state the processes are in. From the ps(1) manpage, D Marks a process in disk (or other short term, uninter- ruptable) wait. Note the use of the word "uninterruptable." I the process would do its thing for the signal it got once out of the "short term" wait, but it is not coming out of it. It's usually a symptom of hardware (disk, disk controller) or network (NFS) trouble. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message