I have, to me, perplexing situation. I am attempting to run Firefox on a CentOS-6.3 virtual machine to which I am connected using an SSH link with X-Forwarding enabled. (ssh -Y userid@host.domain.tld).
The reason I wish to do this is that the vm is used for development an my code coverage analysis tool produces a html format report which is read via the file:// protocol. I thought that if I ran Firefox on that host then the Firefox window would open on my local machine, which it does. I also thought that since that Firefox window was actually running as an instance on the remote vm that the file:// protocol for that Firefox would seek out files on the vm's filesystem, which it does not. Instead that Firefox instance searches the local machine's filesystem and not that of the vm from which it was launched.
This seems counter-intuitive to me. What is going on?
James B. Byrne wrote:
I have, to me, perplexing situation. I am attempting to run Firefox on a CentOS-6.3 virtual machine to which I am connected using an SSH link with X-Forwarding enabled. (ssh -Y userid@host.domain.tld).
The reason I wish to do this is that the vm is used for development an my code coverage analysis tool produces a html format report which is read via the file:// protocol. I thought that if I ran Firefox on that host then the Firefox window would open on my local machine, which it does. I also thought that since that Firefox window was actually running as an instance on the remote vm that the file:// protocol for that Firefox would seek out files on the vm's filesystem, which it does not. Instead that Firefox instance searches the local machine's filesystem and not that of the vm from which it was launched.
This seems counter-intuitive to me. What is going on?
firefox -P --no-remote
The -P is because, assuming you have firefox running, it'll complain about that. Tell it to create a new profile or whatever; I have a test one (and one for CUPS on yet another machine.....
mark
On Thu, Dec 13, 2012 at 9:40 AM, James B. Byrne byrnejb@harte-lyne.ca wrote:
I have, to me, perplexing situation. I am attempting to run Firefox on a CentOS-6.3 virtual machine to which I am connected using an SSH link with X-Forwarding enabled. (ssh -Y userid@host.domain.tld).
The reason I wish to do this is that the vm is used for development an my code coverage analysis tool produces a html format report which is read via the file:// protocol. I thought that if I ran Firefox on that host then the Firefox window would open on my local machine, which it does. I also thought that since that Firefox window was actually running as an instance on the remote vm that the file:// protocol for that Firefox would seek out files on the vm's filesystem, which it does not. Instead that Firefox instance searches the local machine's filesystem and not that of the vm from which it was launched.
This seems counter-intuitive to me. What is going on?
The usual issue with firefox is that if you have an instance running and attempt to start another instance (perhaps with a different DISPLAY) it will instead tell the running instance to open a new window. I've only seen that in the reverse situation - where the remote host has the other copy and you don't see the new window and I'm not sure it makes sense for what you describe. In any case, using freenx and the nx client is a much nicer way to do remote GUI work.
On: Thu Dec 13 15:47:57 UTC 2012 m.roth at 5-cent.us m.roth at 5-cent.us wrote:
firefox -P --no-remote
The -P is because, assuming you have firefox running, it'll complain about that. Tell it to create a new profile or whatever; I have a test one (and one for CUPS on yet another machine.....
mark
Works perfectly. Thank you very much.
James B. Byrne wrote:
On: Thu Dec 13 15:47:57 UTC 2012 m.roth at 5-cent.us m.roth at 5-cent.us wrote:
firefox -P --no-remote
The -P is because, assuming you have firefox running, it'll complain about that. Tell it to create a new profile or whatever; I have a test one (and one for CUPS on yet another machine.....
Works perfectly. Thank you very much.
Excellent. Glad to hear it.
mark