Parallel invocation of postinst script causing a bug?
Dear all,
recently a bug was reported against teTeX which I can't understand and
fix, #396835. I wasn't able to reproduce it so far (although I maybe
encountered it myself months ago, #315762), but the submitter provided
helpful information, among others an output of "ps axf" which really
puzzles me:
13780 ? Ss 0:01 kdeinit Running...
13836 ? S 3:46 \_ konsole [kdeinit]
13838 pts/1 Ss 0:00 | \_ /bin/bash
30006 pts/11 S 0:00 | | \_ bash
11472 pts/11 S+ 0:00 | | \_ apt-get install tetex-extra
12062 pts/11 S+ 0:00 | | \_ /usr/bin/dpkg --status-fd 18 --configure tetex-base tetex-bin tetex-extra
12063 pts/11 S+ 0:00 | | \_ /bin/sh -e /var/lib/dpkg/info/tetex-base.postinst configure
13337 pts/11 R+ 7:06 | | \_ kpsewhich --format=web2c files fmtutil.cnf
30027 pts/11 S 0:00 /bin/sh -e /var/lib/dpkg/info/tetex-bin.postinst configure
30211 pts/11 S 0:00 \_ /bin/sh /usr/bin/fmtutil --all
6929 pts/11 S 0:00 \_ /bin/sh /usr/bin/fmtutil --all
6930 pts/11 S 0:00 \_ /bin/sh /usr/bin/fmtutil --all
6931 pts/11 R 11:09 \_ kpsewhich --var-value=TEXMFMAIN
So it seems two postinst script were running at the same time (note that
tetex-bin depends on tetex-base). Furthermore, the second one seems to
have no parent except init, while the other one has "dpkg --configure
tetex-base tetex-bin..." as its parent.
Does anyone have an idea which kind of error in our packages could have
such a strange effect?
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
Reply to: