Originally posted by silversky
ps aux | grep -i moz brings up the following
root 1857 0.0 0.1 1480 464 pts/1 S 15:17 0:00 grep -i moz
Unfortunately, the pid changes with each change I ps, so I can't kill the process.
Define Similar? There aren't that many directories there... The lock file isn't IN any of them.
Telling me to start mozilla different ways is like telling me how to breathe different ways. It doesn't work that way, unless of course you would like to bother being specific.
Variables? This is a web browser and not a large compiler. Why should a web browser not be able to find its own variables? Why does a lack of variables make my browser not start all of the sudden?!
Chris H. - Keep your cat to yourself.
Okay - that's just the grep process showing up, not mozilla. So you're right that there's no sneaky instance of mozilla running around.
I didn't have anything specific in mind by 'similar'. I can't remember how the directory structure gets set up in mozilla with multiple accounts. I only have one, so my lock file is where I said. If you have multiple accounts I'd hazard there could be lock files in the corresponding places for those other accounts.
Well, I thought I was giving the idea, but maybe not. The problem is I have three mozillas in different places and start it in yet another way or two. My default mozilla came like
So you can issue a command specifying the full path to those and see what happens, or cd to those directory and do the './command' thing. How I actually usually start it is from a symlink that points to ~/bin/mozilla/mozilla where 1.6 lives.
I'm not sure why mozilla needs the variables. It's a very complicated app and it keeps its binary in lib
and has a zillion directories for things. I guess it can be built different ways and all those things can end up in different places so it has to have some way of keeping track of where all the parts of the lizard are.
You say 'all of a sudden' - have you made any system modifications or mods to your configs like your shell? If you can track down anything that changed, that may be the solution.
It also may not be a mozilla issue but the vnc thing. I know nothing about that. (I know very little about any of this - I don't have a solution but I'm hoping some of these suggestions give you ideas for solutions.)