On 01/13/2014 05:50 PM, MR ZenWiz wrote:
On Mon, Jan 13, 2014 at 5:43 PM, goodwin <[email protected]> wrote:
On 01/13/2014 10:16 AM, MR ZenWiz wrote:
I just wrote a simple shell script that clobbers whichever one is
giving me trouble:
#!/bin/bash
# A shell script to kill that annoying runaway
seamonkey/firefox/npviewer that won't die
case `basename $0` in
"seakill") cmd=seamonkey;;
"foxkill") cmd=firefox;;
"npvkill") cmd=npviewer;;
*) echo "Unrecognized command."; exit 1;;
esac
/usr/bin/pkill -9 $cmd
/bin/ps -fC $cmd
what the heck is npviewer and how did it get into this thread?
Collateral damage. After I found the problem with SeaMonkey, it began
to occur occasioinally in Firefox, then later with npviewer, which is
part of the Adobe flash player systems that used to cause hangs,
similar to these (GIYF). I haven't needed npvkill in about two years,
but why remove it if it may ever cause problems again?
Maybe so but hardly on point here - though, thinking about it, maybe I'm
all wet - /anything/ would be on point since it seems to have turned
into a discussion of .lock files - I have no idea where the original
poster stands.
Nice script, good exercise, but better to discover what the cause
actually is.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
