AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20081105131945.7078fc86@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:exch1.onstor.net
NSV:
SSH:
R:<sandrine.boulanger@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	2779531E7C760D4491C96305019FEEB5175C003756@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 5 Nov 2008 13:19:58 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Sandrine Boulanger <sandrine.boulanger@onstor.com>
Subject: Re: installing exum4 package on cougar soak
Message-ID: <20081105131958.7e73a910@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB5175C003756@exch1.onstor.net>
References: <20081105112640.17ff5b21@ripper.onstor.net>
	<2779531E7C760D4491C96305019FEEB5175C003756@exch1.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 5 Nov 2008 11:47:53 -0800 Sandrine Boulanger
<sandrine.boulanger@onstor.com> wrote:

> So what do we do with the exim -q processes? Should we try to kill
> them and see if they reappear?
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, November 05, 2008 11:27 AM
> To: Sandrine Boulanger
> Subject: Re: installing exum4 package on cougar soak
> 
> The stuck exim -q packages are a symptom of the bug, so
> congratulations!  Anyway, I just checked a new version of the package
> into the r401rel branch, and you should use that instead:
> 
> r401rel/linux/Pkgs/binary/Deb/exim4-daemon-custom_4.63-17_mipsel.deb
> 
> This has some additional changes as perscribed by Max that should
> definitely be more correct than the previous ones.
> 
> Thanks,
> 
> a
> 
> PS I also attached the package to this email.  Oh, and kill those
                                                         ^^^^^^^^^^
> exim -q processes before doing the package install.
  ^^^^^^^^^^^^^^^^^

After you install the new package, yes, you can take a look once a week
or so to see if any hung "queue runner" processes like those appear
again.  Or any other hung exim4 processes.

> 
> 
> On Wed, 5 Nov 2008 10:54:04 -0800 Sandrine Boulanger
> <sandrine.boulanger@onstor.com> wrote:
> 
> > Is this OK that the exim4 -q processes don't change?
> > 
> > g11r10:~# ps ax | grep exim
> >   815 ?        S      0:00 /usr/sbin/exim4 -q
> >   824 ?        S      0:03 /usr/sbin/exim4 -q
> >  1111 ?        Ss     0:00 /usr/sbin/exim4 -bd -q30m
> >  9304 pts/0    R+     0:00 grep exim
> > g11r10:~# mkdir -p /usr/share/doc/exim4-custom/daemon
> > g11r10:~#  mkdir -p /usr/share/man/man8 /usr/share/man/man1
> > g11r10:~# mount 10.0.0.222:/s_home/users/sandrineb/private /mnt
> > g11r10:~# dpkg -i /mnt/exim4-daemon-custom_4.63-17_mipsel.deb
> > (Reading database ... 10293 files and directories currently
> > installed.) Preparing to replace exim4-daemon-custom 1:4.63-17
> > (using .../exim4-daemon-custom_4.63-17_mipsel.deb) ... Stopping MTA:
> > exim4_listener. Unpacking replacement exim4-daemon-custom ...
> > Setting up exim4-daemon-custom (4.63-17) ...
> > Starting MTA: exim4.
> > 
> > g11r10:~# umount /mnt
> > g11r10:~# ps ax | grep exim
> >   815 ?        S      0:00 /usr/sbin/exim4 -q
> >   824 ?        S      0:03 /usr/sbin/exim4 -q
> >  9428 ?        Ss     0:00 /usr/sbin/exim4 -bd -q30m
> >  9468 pts/0    R+     0:00 grep exim
> > g11r10:~#
> > 
