On Wed, Nov 17, 2010 at 4:16 PM, Guillem Jover <guil...@debian.org> wrote: > On Wed, 2010-11-17 at 21:33:52 +0100, Andreas Tille wrote: >> On Wed, Nov 17, 2010 at 12:28:54PM -0600, Lucas Nussbaum wrote: >> > It seems that after installation of dict-wn, there's a process that is >> > still >> > running, so destroying the chroot fails. >> >> I'm quoting the relevant part of dict-wn postinst resp. postrm: > >> remove|purge) >> if [ -x /usr/sbin/dictdconfig ]; then dictdconfig -w ;fi >> >> # if [ -x /etc/init.d/dictd ]; then /etc/init.d/dictd restart; fi >> if which invoke-rc.d >/dev/null 2>&1; then >> invoke-rc.d dictd restart >> else >> /etc/init.d/dictd restart >> fi >> exit 0 > >> Can you imagine that this might cause the problem? The other content of >> the package is simply a dictionary. So either the call of dictd init >> script is wrong or dictd itself has a problem. What do you think? > > It's restarting (instead of stoppping) on remove/purge.
Right, because dict-wn is just a database. It detects if a dict-server is installed and restarts it so it is aware of the change in available databases, but the restart was blocked (according to the log) due to the invoke-rc.d policy. This sounds like something (without having looked at the details) that would be prime for triggers instead of having the various database-providing package worry about what the server needs to do. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <james...@debian.org> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktin_jitezhmv0ufotxfde77hc6ocarisbfw5z...@mail.gmail.com
