Your message dated Sat, 31 Mar 2007 13:29:18 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#416902: imapproxy: init script stop action fails
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: imapproxy
Version: 1.2.4-10.1
Severity: serious
# /etc/init.d/imapproxy stop
Not running: imapproxy.
# ps 12192
PID TTY STAT TIME COMMAND
12192 ? Sl 0:06 /usr/sbin/imapproxyd -f /etc/imapproxy.conf
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages imapproxy depends on:
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libncurses5 5.5-5 Shared libraries for terminal hand
ii libssl0.9.8 0.9.8c-4 SSL shared libraries
ii libwrap0 7.6.dbs-13 Wietse Venema's TCP wrappers libra
ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip
imapproxy recommends no packages.
-- debconf information:
imapproxy/imap-server: localhost
--- End Message ---
--- Begin Message ---
Source: up-imapproxy
Version: 1.2.4-10.1
On Sat, Mar 31, 2007 at 12:19:12PM +0100, Sam Morris wrote:
> On Sat, 2007-03-31 at 13:17 +0200, Jeroen van Wolffelaar wrote:
> > On Sat, Mar 31, 2007 at 12:09:59PM +0100, Sam Morris wrote:
> > > # /etc/init.d/imapproxy stop
> > > Not running: imapproxy.
> > >
> > > # ps 12192
> > > PID TTY STAT TIME COMMAND
> > > 12192 ? Sl 0:06 /usr/sbin/imapproxyd -f /etc/imapproxy.conf
> >
> > - Does /var/run/imapproxy.pid exist, and if so, what does it contain?
>
> The wrong pid (8319)
>
> > - With what version of the init script was imapproxy started?
>
> 1.2.4-10 -- I think.
Right, that's a bug in -10 and earlier, fixed in current
testing/unstable, then. The stable version of the initscript does a
killall, so would work too.
--Jeroen
--
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
--- End Message ---
