On Mon, Jul 15, 2013 at 06:01:36PM -0000, John Reid wrote:
> Good point, I didn't check the output too closely. 15673 is the bash
> shell I started banshee from:
>
> ~/Downloads
> john@W530$ ps -ef|grep 15673
> john 4724 4624 0 18:59 pts/21 00:00:00 grep --color=auto 15673
> john 15673 10712 0 Jul09 pts/7 00:00:00 bash
> john 25995 15673 4 13:00 pts/7 00:14:35 [banshee] <defunct>
>
> However banshee is not responding to Ctrl-C in the bash terminal nor to
> kills so what to do?
>
> ~/Downloads
> john@W530$ kill -9 25995
> ~/Downloads
> john@W530$ kill -15 25995
> ~/Downloads
> john@W530$ kill 25995
> ~/Downloads
> john@W530$ ps -ef|grep 15673
> john 4780 4624 0 19:00 pts/21 00:00:00 grep --color=auto 15673
> john 15673 10712 0 Jul09 pts/7 00:00:00 bash
> john 25995 15673 4 13:00 pts/7 00:14:35 [banshee] <defunct>
Try killing the bash process itself. If that doesn't work, keep following the
trail up until you reach 1. There seems to be a parent process of that bash
process.
On Mon, Jul 15, 2013 at 06:01:36PM -0000, John Reid wrote:
> Good point, I didn't check the output too closely. 15673 is the bash
> shell I started banshee from:
>
> ~/Downloads
> john@W530$ ps -ef|grep 15673
> john 4724 4624 0 18:59 pts/21 00:00:00 grep --color=auto 15673
> john 15673 10712 0 Jul09 pts/7 00:00:00 bash
> john 25995 15673 4 13:00 pts/7 00:14:35 [banshee] <defunct>
>
> However banshee is not responding to Ctrl-C in the bash terminal nor to
> kills so what to do?
>
> ~/Downloads
> john@W530$ kill -9 25995
> ~/Downloads
> john@W530$ kill -15 25995
> ~/Downloads
> john@W530$ kill 25995
> ~/Downloads
> john@W530$ ps -ef|grep 15673
> john 4780 4624 0 19:00 pts/21 00:00:00 grep --color=auto 15673
> john 15673 10712 0 Jul09 pts/7 00:00:00 bash
> john 25995 15673 4 13:00 pts/7 00:14:35 [banshee] <defunct>
Try killing the bash process itself. If that doesn't work, keep following the
trail up until you reach 1. There seems to be a parent process of that bash
process.
--
Kind regards,
Loong Jin