How can I prevent a 'remote' Firefox from using the 'local' Firefox instead of starting a real remote one?
I sometimes need to run a specific version of Firefox which I have installed on Solaris here, it has a very specific version of Java which I need for a particular Oracle plugin. Now I have a Linux desktop system I run a Linux Firefox as my everyday browser.
What I want to be able to do is run the Solaris Firefox on my Linux display without having to first shut the Linux Firefox down. By default when you try and run the (remote) Solaris Firefox it will look and see that you have a copy of Firefox running on the same display and just sends the URL you have given it to that display rather then running a new copy of Firefox.
How do I force it to run?
Interesting
I have been bitten by the firefox behaviour to spawn another thread from the existing firefox session rather than open a new instance. But I am confused as to how this behaviour you describe is even possible across local and remote machines. I just had to try it and you are right.
If for example I launch my local copy of firefox and then ssh -XC over to a machine at my office and launch a copy of firefox from there I get the usual delay I would expect with X forwarding a hungry app over ssh and DSL and then as you say and contrary to what I expected another instance of my local version of firefox pops up.
Fortunately there seems to be a cure
Allegedly setting the environment variable MOZ_NO_REMOTE to 1 on the remote machine before launching firefox will fix it
Further to that on firefox 2 you can simply add the option when launching the remote instance i.e 'firefox -no-remote'
On Mon, Mar 19, 2007 at 07:38:39PM +0000, Wayne Stallwood wrote:
Interesting
I have been bitten by the firefox behaviour to spawn another thread from the existing firefox session rather than open a new instance. But I am confused as to how this behaviour you describe is even possible across local and remote machines. I just had to try it and you are right.
It's always been that way with the Netscape/Mozilla/Firefox family as far as I know.
If for example I launch my local copy of firefox and then ssh -XC over to a machine at my office and launch a copy of firefox from there I get the usual delay I would expect with X forwarding a hungry app over ssh and DSL and then as you say and contrary to what I expected another instance of my local version of firefox pops up.
Fortunately there seems to be a cure
Allegedly setting the environment variable MOZ_NO_REMOTE to 1 on the remote machine before launching firefox will fix it
Aha, yes, a quick Google for MOZ_NO_REMOTE confirms this, thank you!
Further to that on firefox 2 you can simply add the option when launching the remote instance i.e 'firefox -no-remote'
Makes sense as the way to explicitly get a connection to an existing remote copy of Firefox is '-remote'.
-
Eur Ing Chris Green -
Wayne Stallwood