Package: xpdf Version: 3.03-2 Severity: normal Dear Maintainer,
xpdf's wrapper script should start xpdf.real using 'exec', since it is the last thing the script does. This means an extra process is not kept running, and the process will respond properly to signals. Regarding the signal issue, I have a shell script that starts xpdf in the background and records its PID with $!. When I no longer need xpdf running, I send a signal to the PID recorded from $! when the process was launched. Since that PID is actually the wrapper script and not the real xpdf process, the signals are ignored. Using 'exec' in the script solves this problem by making the xpdf.real process have the same PID as the wrapper script. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xpdf depends on: ii lesstif2 1:0.95.2-1 ii libc6 2.13-18 ii libgcc1 1:4.6.1-8 ii libpoppler13 0.16.7-2 ii libstdc++6 4.6.1-8 ii libx11-6 2:1.4.4-1 ii libxt6 1:1.1.1-2 Versions of packages xpdf recommends: ii gsfonts-x11 <none> ii poppler-data <none> ii poppler-utils 0.16.7-2 xpdf suggests no packages. -- no debconf information
