Walter Dnes wrote:
>   I vaguely remember a while ago, somebody on this list asked about
> running separate instances of Firefox.  I finally figured out how to run
> separate instances of Firefox, as ***COMPLETELY SEPARATE PROCESSES***.
> Namely, that you need ***A SEPARATE PROFILE FOR EACH INSTANCE***.  Let's
> start with 2 profiles "trusted" and "default".  From the command line,
> execute the following commands...
>
> firefox -new-instance -P trusted &
> firefox -new-instance -P default &
> ps -ef | grep firefox
>
>   You won't need the "&" if you launch from a desktop or window-manager
> launcher.  In the above example, I launched 2 instances of Firefox, and
> verified their existance by running "ps -ef | grep firefox".
>
>   So if you have some sites that you visit regularly, you can have a
> separate profile for each one.  This has some advantages...
>
> 1) You can have totally different customized setups (including different
> add-ons) for each site.
>
> 2) Profiles, including cookies, are stored in separate directories.
> Therefore third-party cookies left by trackers when you're on site A
> using profile A, will not be readable by the same third-party when
> you're on site B, using profile B, making tracking you more difficult
> and less reliable... one... two... three... aaaaawwwwwww.
>
> 3) If you have a whole bunch of websites open, and one of them crashes
> Firefox, or hangs it so you need to kill it, you don't end up taking
> down all your browsers.
>

That I think was me.  Also, if you close one and it doesn't die
correctly, you can use this little trick, as a script in my case, to
find the process for each one that is running.

ls -al /home/<user name here>/.mozilla/firefox/*/lock 

For example, on mine it returns this, name somewhat edited:

root@fireball / # /root/firefox
ls -al /home/dale/.mozilla/firefox/*/lock
 
lrwxrwxrwx 1 dale users 16 Jun 22 22:57
/home/dale/.mozilla/firefox/4p9tgzd5.MOD/lock -> 127.0.0.1:+28060
lrwxrwxrwx 1 dale users 16 Jun 22 22:53
/home/dale/.mozilla/firefox/ar78vn2c.default/lock -> 127.0.0.1:+27753
lrwxrwxrwx 1 dale users 16 Jun 22 23:58
/home/dale/.mozilla/firefox/hmnj07pv.Greet staff/lock -> 127.0.0.1:+31137
root@fireball / #  

Notice the process number on the end?  If say I close the default but it
doesn't die as it should, I can do this:

kill 27753

The other processes are still running.  Also, if it is dead but it
didn't remove the lock file, just use rm instead of ls and remove the
options of course. 

Hope that helps you as much as it did me.  ;-) 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how 
you interpreted my words!


Reply via email to