On ons, 2012-05-23 at 07:56 +0200, Detlev Brodowski wrote: > Package: dirmngr > Version: 1.1.0-3 > Severity: important > > Hello maintainer, > > The init script starts the daemon but don't write the pid to the pid file. > Therefore the stop procedure cannot stop the daemon. > > I have reproduced this behavior with dash as /bin/sh and bash as /bin/sh with > different output. > > dash: > root@pluto3:~# /etc/init.d/dirmngr start > [....] Starting DirMngr: dirmngr/etc/init.d/dirmngr: 1: eval: not found > /etc/init.d/dirmngr: 1: eval: 0]DIRMNGR_INFO=/var/run/dirmngr/socket:26899:1: > not found > .. ok > > bash: > root@pluto3:~# /etc/init.d/dirmngr start > [....] Starting DirMngr: dirmngr/etc/init.d/dirmngr: Zeile 36: $'\E[11': > Kommando nicht gefunden. > /etc/init.d/dirmngr: Zeile 36: > 0]DIRMNGR_INFO=/var/run/dirmngr/socket:27054:1: Datei oder Verzeichnis nicht > gefunden > .. ok
It works for me. Can you run it through bash -x and/or dash -x to see what's happening? It looks like the lsb-base output might be interfering. Could you try downgrading that to 4.1+Debian3 to see if it makes a difference? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
