Donald D Henson wrote: > I seem to have gotten myself into a situation where a Firefox process > will not die nor will it display anything. (The problem seems to have > something to do with You Tube.) When I try to start up another instance > of Firefox, I get an error message that tells me to either close the > current process or to reboot the system. Rebooting is not a good > solution. I remember from the 'old days' that there is a cli command to > identify a process id and another one to kill a process. I've searched > my memory and the User Manual but cannot identify those two commands. > Any assistance will be sincerely appreciated.
It probably doesn't actually have a process running. It sees the file ~/.mozilla/firefox/05uz5zzz.default/.parentlock and thinks it is still running (so even a reboot might not fix it). If you don't actually see a firefox process, try deleting that file (using, of course, your own special .default folder). -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Daemon Dancing in the Dark, a FreeBSD weblog: http://freebsd.amazingdev.com/blog/ UNIX is user-friendly. It's just a bit picky about who its friends are. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
