Date: Wed, 29 Mar 2006 21:15:58 -0600 From: Paul Schmehl <pauls@utdallas.edu> To: freebsd-ports@freebsd.org Subject: Re: Problem stopping a program Message-ID: <E47528F6C6B025B2D093C0C4@Paul-Schmehls-Computer.local> In-Reply-To: <200603300300.53523.danny@ricin.com> References: <6F8EC8DCFAC4D47258FEF35B@Paul-Schmehls-Computer.local> <200603300300.53523.danny@ricin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--==========E8DF9E425FD2508AC6E0========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On March 30, 2006 3:00:53 AM +0200 Danny Pansters <danny@ricin.com> = wrote: >> >> Here's an example: /usr/local/etc/rc.d/sguild.sh restart >> Stopping sguild >> Waiting for PIDS: 4554 4558 4559, 4554 4558 4559, 4554 4558 4559, 4554 >> 4558 4559, 4554 4558 4559, 4554 4558 4559, 4554 4558 4559, 4554 4558 >> 4559, 4554 4558 4559, 4554 4558 4559, 4554 4558 4559, 4554 4558 4559, >> 4554 4558 4559, 4554 4558 4559, >> >> This will go on indefinitely. If I kill the process and then try >> restarting again, the child processes are gone, but the parent process = is >> not. > > Try pkill/pgrep (p=3Dparent) ? > That seems a bit of overkill. I'd have to make pkill a RUN_DEPENDS,=20 forcing the user to install it just to kill the process. As it turns out,=20 it appears that TERM won't kill the process if it's been running for a=20 while, but KILL will. I've notified the developer. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/ --==========E8DF9E425FD2508AC6E0==========--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E47528F6C6B025B2D093C0C4>