Le mer. 10 avril 2013 08:56:40 CEST, Jaap Karssenberg a écrit :
We use the temp dir given by the standard "tempfile" module, it
depends on environment variables (see
http://docs.python.org/2/library/tempfile.html). Apparently the
firefox process has another environment than the terminal process.
Sounds like I should take care in zim that the socket location is
uniquely defined and not depending on this temporary file. But not
sure what would be a robust way to determine such a location.
It's seems to be a recent move in Fedora : the TMPDIR variable
pointing to /var/tmp is hard coded in Firefox script :
## Use $MOZ_TMPDIR if set. Otherwise use /var/tmp instead of /tmp
## because of 1GB /tmp limit in Fedora 18 and later.
## See: https://bugzilla.redhat.com/show_bug.cgi?id=867073
I could define the $MOZ_TMPDIR variable pointing to /tmp, but it will
mean that an addon change the behavior of all Firefox, which I think
will not be quit good.
I continue my investigation on how nsIProcess (interface that provides
a way to run third party applications from Firefox) works, to see if I
can define a tmp dir only for the process I create to run Zim.
Mailing list: https://launchpad.net/~zim-wiki
Post to : email@example.com
Unsubscribe : https://launchpad.net/~zim-wiki
More help : https://help.launchpad.net/ListHelp