Talk:Firefox/Profile on RAM

From ArchWiki
Latest comment: 4 December 2023 by Barraponto in topic Profile-sync-daemon


How about pointing out a few drawbacks like "putting browser profile into /tmp poses a security risk --- other users can now see it?" All3fox (talk) 07:17, 30 August 2013 (UTC)Reply[reply]

We can have tmpfs with privacy AFAIK. By making use of overlayfs which has acl. Can be enabled in e.g. profile-sync-daemon or anything-sync-daemon.--kozaki (talk) 17:01, 22 August 2016 (UTC)Reply[reply]


I think this line


in the script should be changed to


, or the CRON job will fail, because $USER is not set. But as I'm using another distro I don't know wheter it is working in ARCH, so I won't change that line now. Hope I get some feedback here. Kovacssanya (talk) 10:33, 22 November 2013 (UTC)Reply[reply]

A more simple way of using firefox-sync is to make a script like this:


i.e merging profiles before launching firefox and after closing it. It has its downsides but it is easier. Kisame217 (talk) 12:52, 19 September 2014 (UTC)Reply[reply]

.profile instead of .bash_profile

This is a comment for the "Sync at login/logout" section. Firefox is loaded by the GUI, which does not necessarily log in through bash (for example GUI users might prefer to login with gdm for GNOME). However .bash_profile is only ran when someone logs in from the command-line.

It would thus be helpful to add that when you have something like gdm installed (or don't log-in with bash when you use Firefox), you have to call firefox-sync from ~/.profile (in the case of GNOME), not in ~/.bash_profile (or ~/.bash_login).

—This unsigned comment is by Makhlaghi (talk) 22:25, 20 July 2016‎. Please sign your posts with ~~~~!

.bash_logout not being called

I see .bash_logout is not called neither when I shutdown nor reboot. My history is not remembered since I tried this article 'Firefox on RAM'. Maybe with KDE/plasma one needs to use systemd[1]? [1]

--Nicoadamo (talk) 17:11, 10 September 2016 (UTC)Reply[reply]

Firefox's new Cache relies on browser.dIsk.cache

If setting browser.cache.disk.enable = false, one then loose browser.cache.use_new_backend (FF 32 and above « new cache system ») stability and performance improvements. Since the latter relies on the former being enabled.--kozaki (talk) 17:07, 22 August 2016 (UTC)Reply[reply]


How is this different from using profile-sync-daemon? Should we mention the daemon? Capi Etheriel (talk) 14:43, 4 December 2023 (UTC)Reply[reply]