Date: Sat, 10 Jun 2000 12:55:45 -0700 From: "Crist J. Clark" <cjc@earthlink.net> To: Xavier Lumine <dmyshkin@hotmail.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: bug report with malfunctioning KILL of cvsup process Message-ID: <20000610125545.C1197@dialin-client.earthlink.net> In-Reply-To: <20000610124323.42179.qmail@hotmail.com>; from dmyshkin@hotmail.com on Sat, Jun 10, 2000 at 08:43:23AM -0400 References: <20000610124323.42179.qmail@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000610125545.C1197>