Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)
Dnia czwartek, 23 listopada 2006 12:09, Julian Gilbey napisał:
> On Thu, Nov 23, 2006 at 11:30:39AM +0100, Marcin Juszkiewicz wrote:
> > Dnia środa, 22 listopada 2006 18:43, Frank Küster napisał:
> > kdebug:kpse_normalize_path (/home/hrw//texmf) => 1
> It seems that $TEXMFHOME is expanding to /home/hrw//texmf with an
> extra slash in it, meaning that it's searching your entire home
> directory (a silly thing to do), so I suspect an extra slash somewhere
> here. You may have a corrupted/modified version of
> /etc/texmf/texmf.d/05TeXMF.cnf which is causing this.
12:57 hrw@work:hrw$ grep -v "^%" /etc/texmf/texmf.d/05TeXMF.cnf
TEXMFMAIN = /usr/share/texmf
TEXMFDIST = /usr/share/texmf-{texlive,tetex}
TEXMFLOCAL = /usr/local/share/texmf
TEXMFSYSVAR = /var/lib/texmf
TEXMFSYSCONFIG = /etc/texmf
TEXMFHOME = $HOME/texmf
TEXMFVAR = $HOME/.texmf-var
TEXMFCONFIG = $HOME/.texmf-config
TEXMF = {$TEXMFCONFIG,$TEXMFVAR,$TEXMFHOME,$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFLOCAL,!!$TEXMFMAIN,!!$TEXMFDIST}
SYSTEXMF = $TEXMFLOCAL;$TEXMFMAIN;$TEXMFDIST
VARTEXFONTS = /tmp/texfonts
TEXMFDBS = $TEXMFHOME;$TEXMFSYSVAR;$TEXMFLOCAL;$TEXMFMAIN;$VARTEXFONTS;$TEXMFDIST
> Could you please now also send the the output of:
> grep '^TEXMFHOME =' /etc/texmf/texmf.cnf
12:55 hrw@work:hrw$ grep '^TEXMFHOME =' /etc/texmf/texmf.cnf
TEXMFHOME = $HOME/texmf
> echo $HOME
/home/hrw/
> > and here it start to go through filesystem and loops in kernel build
> > due to symlinks:
> > kdebug:hash_lookup(/home/hrw/src/linux/debian/linux-image-2.6.19-rc2/l
> >ib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/
> >2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/
> >source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debi
> >an/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-im
> >age-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-
> >rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/mod
> >ules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19
> >-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source
> >/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/lin
> >ux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.
> >6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/li
> >b/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2
> >.6.19-rc2/source/drivers/infiniband/ulp) => (nil)
> This is something which kpathsea is not designed to guard against.
> Hmm. Perhaps it should, say, keep track of any symlinks it meets in a
> path, and if it meets the identical symlink again, stop following it.
> That would require some significant changes to libkpathsea, though.
> Also, I believe this is quite a Unix-specific issue.
> Then again, symlink loops like this are just plain evil.
Blame kernel-package?
12:58 hrw@work:hrw$ pwd
/home/hrw
12:58 hrw@work:hrw$ ll src/linux/debian/linux-image-2.6.19-rc5/lib/modules/2.6.19-rc5/source
lrwxrwxrwx 1 hrw pavilon 19 2006-11-10 15:51 src/linux/debian/linux-image-2.6.19-rc5/lib/modules/2.6.19-rc5/source -> /home/hrw/src/linux
--
Reply to: