Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#10492 - texlive-core putting temporary files under /root/.texmf-var
Attached to Project:
Community Packages
Opened by Alberto Simoes (ambs) - Saturday, 24 May 2008, 21:44 GMT
Last edited by Francois Charette (Firmicus) - Saturday, 25 October 2008, 20:01 GMT
Opened by Alberto Simoes (ambs) - Saturday, 24 May 2008, 21:44 GMT
Last edited by Francois Charette (Firmicus) - Saturday, 25 October 2008, 20:01 GMT
|
DetailsDescription:
Hello. latex (kpathsea, and other tools) are creating temporary files under /root/.texmf-var and other similar directories. It would be great it these files were creates somewhere under /var in a world-writable directory. As it is, if you want to run latex from a CGI script, you need to give permissions to everybody to write on that path. Cheers Alberto |
This task depends upon
Closed by Francois Charette (Firmicus)
Saturday, 25 October 2008, 20:01 GMT
Reason for closing: Upstream
Additional comments about closing: This is an upstream issue IMHO.
Also texlive is no longer in community :)
Saturday, 25 October 2008, 20:01 GMT
Reason for closing: Upstream
Additional comments about closing: This is an upstream issue IMHO.
Also texlive is no longer in community :)
Unfortunately I am a little lost with that problem, but probably you can help me to find out exactly what is going on.
I just have a php script that calls pdflatex. The php script runs under the default apache configuration for Arch that (I think) is not run by root. And in fact, it doesn't, or it would have permissions to write under /root. Thus, probably a homeless user (like nobody) triggers this behaviour.
Cheers
Alberto
What I am calling is latex, dvips and then gs.
When calling latex it calls internal tools to create fonts. I think that those are the tools trying to write on that directory.
And by the way, what do you mean by the -sys alternatives?
Thanks
Alberto
That does not happen to me, on my system these stuff goes to /opt/texlive/texmf-var/.
There are tools like fmtutil and updmap that have a -sys variant (fmtutil-sys, updmap-sys).
I would like to suggest that you make a backup of /root/.texmf-var, delete it and do a updmap-sys as root. Afterwards do a latex-run on a document that is known as a font creating one. I think the internal stuff should go to /opt/texlive/texmf-var/ then. Having that tree world writable is less harmful than having /root world writable.
Or you can try to redefine the variable TEXMFSYSVAR in /opt/texlive/texmf/web2c/texmf.cnf to /var/texmf-var or the like.
Removed that directory. Run updmap-sys as root. When running latex, it tries to make fonts on $HOME/.texmf-var (using the apache user).
Accordingly with
/opt/texlive/texmf/web2c/texmf.cnf
the variable
TEXMFVAR = $HOME/.texmf-var
But it is weird that $HOME for apache is /root/
At the moment changed it to
TEXMFVAR = /tmp/.texmf-var
:-/
Cheers
and this should be used instead of $TEXMFVAR (= $HOME/.texmf-var) when the user is root.
To generate bitmap fonts the variable $VARTEXFONTS is used anyway, which is set by default to /var/tmp/texfonts.
Are you sure you don't have some texmf.cnf under $TEXMFLOCAL which changes those default settings?
Well, a find on the system for texmf.cnf returned no other path than
/opt/texlive/texmf/web2c/texmf.cnf
In any case, I am having this same problem in other Arch installation.