Bug#453958: Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
On Tue, Feb 12, 2008 at 08:36:11PM +0100, Kevin Baradon wrote: Le jeudi 17 janvier 2008, Marc Haber a écrit : user [EMAIL PROTECTED] usertags #453958 close-20080331 usertags #449287 close-20080331 thanks On Sat, Dec 01, 2007 at 02:38:54PM +0100, Andreas Metzler wrote: On 2007-12-01 Andreas Metzler [EMAIL PROTECTED] wrote: [] I can reproduce this, the error is generated when killproc invokes /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5 --quiet --oknodo which is dpkg bug 157305. (I am using a block instead of reassigning, too keep the bug visible in exim.) #157305 was fixed on January 8, and I do not see the issue any more. Can the original submitters please take a look and comment? Hello, Bug is still present here in sid (updated today). kev1:/home/kevin# invoke-rc.d exim4 start Starting MTA: exim4. kev1:/home/kevin# ps aux | grep exim4 102 2879 0.0 0.1 6020 916 ?Ss 20:32 0:00 /usr/sbin/exim4 -bd -q30m root 2943 0.0 0.1 2444 760 pts/1S+ 20:32 0:00 grep exim4 kev1:/home/kevin# invoke-rc.d exim4 stop Stopping MTA:/sbin/start-stop-daemon: warning: failed to kill 2879: No such process exim4_listener. kev1:/home/kevin# ps aux | grep exim4 root 3033 0.0 0.1 2444 764 pts/1S+ 20:32 0:00 grep exim4 kev1:/home/kevin# invoke-rc.d exim4 stop Stopping MTA:. kev1:/home/kevin# ps aux | grep exim4 kev1:/home/kevin# Let me known if you need additional information. I'd like to know versions of exim4-base, dpkg and lsb-base installed, and the contents of /etc/default/exim4 and /var/run/exim.pid What does happen when you (with a running exim) invoke /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5 --quiet --oknodo? Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: Bug#453958: Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
Le mercredi 13 février 2008, Marc Haber a écrit : On Tue, Feb 12, 2008 at 08:36:11PM +0100, Kevin Baradon wrote: Le jeudi 17 janvier 2008, Marc Haber a écrit : user [EMAIL PROTECTED] usertags #453958 close-20080331 usertags #449287 close-20080331 thanks On Sat, Dec 01, 2007 at 02:38:54PM +0100, Andreas Metzler wrote: On 2007-12-01 Andreas Metzler [EMAIL PROTECTED] wrote: [] I can reproduce this, the error is generated when killproc invokes /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5 --quiet --oknodo which is dpkg bug 157305. (I am using a block instead of reassigning, too keep the bug visible in exim.) #157305 was fixed on January 8, and I do not see the issue any more. Can the original submitters please take a look and comment? Hello, Bug is still present here in sid (updated today). kev1:/home/kevin# invoke-rc.d exim4 start Starting MTA: exim4. kev1:/home/kevin# ps aux | grep exim4 102 2879 0.0 0.1 6020 916 ?Ss 20:32 0:00 /usr/sbin/exim4 -bd -q30m root 2943 0.0 0.1 2444 760 pts/1S+ 20:32 0:00 grep exim4 kev1:/home/kevin# invoke-rc.d exim4 stop Stopping MTA:/sbin/start-stop-daemon: warning: failed to kill 2879: No such process exim4_listener. kev1:/home/kevin# ps aux | grep exim4 root 3033 0.0 0.1 2444 764 pts/1S+ 20:32 0:00 grep exim4 kev1:/home/kevin# invoke-rc.d exim4 stop Stopping MTA:. kev1:/home/kevin# ps aux | grep exim4 kev1:/home/kevin# Let me known if you need additional information. I'd like to know versions of exim4-base, dpkg and lsb-base installed, and the contents of /etc/default/exim4 and /var/run/exim.pid Hello, Here are all informations you wanted: ii exim44.69-2meta-package to ease Exim MTA (v4) installation ii exim4-base 4.69-2support files for all Exim MTA (v4) packages ii exim4-config 4.69-2 configuration for the Exim MTA (v4) ii exim4-daemon-light 4.69-2lightweight Exim MTA (v4) daemon ii dpkg 1.14.7package maintenance system for Debian ii lsb-base 3.1-24Linux Standard Base 3.1 init script functionality ii lsb-release 3.1-24Linux Standard Base version reporting utility /etc/default/exim4 contents: --x8 # /etc/default/exim4 EX4DEF_VERSION='' # 'combined' - one daemon running queue and listening on SMTP port # 'no' - no daemon running the queue # 'separate' - two separate daemons # 'ppp' - only run queue with /etc/ppp/ip-up.d/exim4. # 'nodaemon' - no daemon is started at all. # 'queueonly' - only a queue running daemon is started, no SMTP listener. # setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4 QUEUERUNNER='combined' # how often should we run the queue QUEUEINTERVAL='30m' # options common to quez-runner and listening daemon COMMONOPTIONS='' # more options for the daemon/process running the queue (applies to the one # started in /etc/ppp/ip-up.d/exim4, too. QUEUERUNNEROPTIONS='' # special flags given to exim directly after the -q. See exim(8) QFLAGS='' # options for daemon listening on port 25 SMTPLISTENEROPTIONS='' --x8 /var/run/exim.pid: there is no such file, but there is a /var/run/exim4/exim.pid file: -rw-r--r-- 1 root Debian-exim 5 fév 13 19:49 /var/run/exim4/exim.pid Its contents: --x8 4982 --x8 What does happen when you (with a running exim) invoke /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5 --quiet --oknodo? [EMAIL PROTECTED]:~$ ps aux | grep exim4 102 4982 0.0 0.1 6020 716 ?Ss 19:49 0:00 /usr/sbin/exim4 -bd -q30m kevin32189 0.0 0.1 2444 756 pts/1R+ 20:11 0:00 grep exim4 kev1:/home/kevin# /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5 --quiet --oknodo /sbin/start-stop-daemon: warning: failed to kill 4982: No such process kev1:/home/kevin# ps aux | grep exim4 root 2488 0.0 0.1 2444 764 pts/1S+ 20:15 0:00 grep exim4 kev1:/home/kevin# ls -l /var/run/exim4/ total 4 -rw-r--r-- 1 root Debian-exim 5 fév 13 19:49 exim.pid kev1:/home/kevin# cat /var/run/exim4/exim.pid 4982 Despite of the error message, process is killed. But its pidfile is still there. Greetings Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: Bug#453958: Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
On 2008-02-13 Kevin Baradon [EMAIL PROTECTED] wrote: Le mercredi 13 février 2008, Marc Haber a écrit : On Tue, Feb 12, 2008 at 08:36:11PM +0100, Kevin Baradon wrote: [...] #157305 was fixed on January 8, and I do not see the issue any more. Can the original submitters please take a look and comment? [...] Bug is still present here in sid (updated today). [...] Here are all informations you wanted: [...] ii dpkg 1.14.7package maintenance system for Debian That is ancient (for sid). The respective bug was fixed in 1.14.15, uploaded on Mon, 07 Jan 2008. Please upgrade and recheck. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: Bug#453958: Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
On Wednesday 13 February 2008, Marc Haber wrote:
Bug is still present here in sid (updated today).
kev1:/home/kevin# invoke-rc.d exim4 start
Starting MTA: exim4.
kev1:/home/kevin# ps aux | grep exim4
102 2879 0.0 0.1 6020 916 ?Ss 20:32
0:00 /usr/sbin/exim4 -bd -q30m
root 2943 0.0 0.1 2444 760 pts/1S+ 20:32 0:00 grep
exim4 kev1:/home/kevin# invoke-rc.d exim4 stop
Stopping MTA:/sbin/start-stop-daemon: warning: failed to kill 2879: No
such process
exim4_listener.
kev1:/home/kevin# ps aux | grep exim4
root 3033 0.0 0.1 2444 764 pts/1S+ 20:32 0:00 grep
exim4 kev1:/home/kevin# invoke-rc.d exim4 stop
Stopping MTA:.
kev1:/home/kevin# ps aux | grep exim4
kev1:/home/kevin#
Let me known if you need additional information.
I'd like to know versions of exim4-base, dpkg and lsb-base installed,
and the contents of /etc/default/exim4 and /var/run/exim.pid
For what it's worth, I'm not seeing any errors ATM. Not on system shutdown
and also not when I run '{/etc/init.d/,invoke-rc.d }exim4 {stop,start}'
manually.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: Bug#453958: Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
Le mercredi 13 février 2008, Marc Haber a écrit : On Wed, Feb 13, 2008 at 08:19:10PM +0100, Kevin Baradon wrote: ii dpkg 1.14.7 package maintenance system for Debian Current sid and lenny have 1.14.16.6; the Bug you are experiencing was fixed in 1.14.15. I still intend to close this bug by the end of March 2008. Greetings Marc My bad, dpkg was pinned in /etc/apt/preferences :/ Upgraded it and bug is not reproducible. So consider it is fixed. Sorry for the noise. Greetings. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: Bug#453958: Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
On Wed, Feb 13, 2008 at 08:19:10PM +0100, Kevin Baradon wrote: ii dpkg 1.14.7package maintenance system for Debian Current sid and lenny have 1.14.16.6; the Bug you are experiencing was fixed in 1.14.15. I still intend to close this bug by the end of March 2008. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
Le jeudi 17 janvier 2008, Marc Haber a écrit : user [EMAIL PROTECTED] usertags #453958 close-20080331 usertags #449287 close-20080331 thanks On Sat, Dec 01, 2007 at 02:38:54PM +0100, Andreas Metzler wrote: On 2007-12-01 Andreas Metzler [EMAIL PROTECTED] wrote: [] I can reproduce this, the error is generated when killproc invokes /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5 --quiet --oknodo which is dpkg bug 157305. (I am using a block instead of reassigning, too keep the bug visible in exim.) #157305 was fixed on January 8, and I do not see the issue any more. Can the original submitters please take a look and comment? Hello, Bug is still present here in sid (updated today). kev1:/home/kevin# invoke-rc.d exim4 start Starting MTA: exim4. kev1:/home/kevin# ps aux | grep exim4 102 2879 0.0 0.1 6020 916 ?Ss 20:32 0:00 /usr/sbin/exim4 -bd -q30m root 2943 0.0 0.1 2444 760 pts/1S+ 20:32 0:00 grep exim4 kev1:/home/kevin# invoke-rc.d exim4 stop Stopping MTA:/sbin/start-stop-daemon: warning: failed to kill 2879: No such process exim4_listener. kev1:/home/kevin# ps aux | grep exim4 root 3033 0.0 0.1 2444 764 pts/1S+ 20:32 0:00 grep exim4 kev1:/home/kevin# invoke-rc.d exim4 stop Stopping MTA:. kev1:/home/kevin# ps aux | grep exim4 kev1:/home/kevin# Let me known if you need additional information. Kevin Otherwise, I intend to close this bug by the end of March 2008. Greetings Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
On Thursday 17 January 2008, Marc Haber wrote: #157305 was fixed on January 8, and I do not see the issue any more. Can the original submitters please take a look and comment? Looks like the issue is gone. Cool. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
user [EMAIL PROTECTED] usertags #453958 close-20080331 usertags #449287 close-20080331 thanks On Sat, Dec 01, 2007 at 02:38:54PM +0100, Andreas Metzler wrote: On 2007-12-01 Andreas Metzler [EMAIL PROTECTED] wrote: [] I can reproduce this, the error is generated when killproc invokes /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5 --quiet --oknodo which is dpkg bug 157305. (I am using a block instead of reassigning, too keep the bug visible in exim.) #157305 was fixed on January 8, and I do not see the issue any more. Can the original submitters please take a look and comment? Otherwise, I intend to close this bug by the end of March 2008. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
On 2007-11-28 Frans Pop [EMAIL PROTECTED] wrote:
severity 449287 important
thanks
I've been seeing the same issue for some time on several systems,
therefore raising priority.
Here's the debug (set -x) output for the stop command during shutdown.
Hope it helps.
At first glance, the problem seems to be that first 'killproc' is being
called and later also start-stop-daemon. And then later there also a
'kill -0'...
[...]
+ /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5
--quiet --oknodo
/sbin/start-stop-daemon: warning: failed to kill 2121: No such process
+ status=0
[...]
Hello,
I can reproduce this, the error is generated when killproc invokes
/sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5
--quiet --oknodo
It is easy to reproduce, start exim, invoke the abovementioned s-s-d
command. stracing s-s-d seems to suggest that s-s-d expects exim4 to
remove the pidfile when it terminates, but exim does not. s-s-d then
tries to terminate exim4 *again* and fails.
4418 open(/var/run/exim4/exim.pid, O_RDONLY|O_LARGEFILE) = 3
4418 fstat64(3, {st_dev=makedev(8, 7), st_ino=11010177, st_mode=S_IFREG|0644,
st_nlink=1, st_uid=0, st_gid=102, st_blksize=4096, st_blocks=8, st_size=5,
st_atime=2007/12/01-13:19:33, st_mtime=2007/12/01-13:19:33,
st_ctime=2007/12/01-13:19:33}) = 0
4418 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0xff9ee7c8) = 0xf7f42000
4418 read(3, 4411\n, 4096) = 5
4418 close(3) = 0
4418 munmap(0xf7f42000, 4096) = 0
4418 kill(4411, SIGTERM) = 0
4418 gettimeofday({1196511580, 568567}, NULL) = 0
4418 gettimeofday({1196511580, 568589}, NULL) = 0
4418 open(/var/run/exim4/exim.pid, O_RDONLY|O_LARGEFILE) = 3
4418 fstat64(3, {st_dev=makedev(8, 7), st_ino=11010177, st_mode=S_IFREG|0644,
st_nlink=1, st_uid=0, st_gid=102, st_blksize=4096, st_blocks=8, st_size=5,
st_atime=2007/12/01-13:19:40, st_mtime=2007/12/01-13:19:33,
st_ctime=2007/12/01-13:19:33}) = 0
4418 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0xff9ee7c8) = 0xf7f42000
4418 read(3, 4411\n, 4096) = 5
4418 close(3) = 0
4418 munmap(0xf7f42000, 4096) = 0
4418 kill(4411, SIG_0) = -1 ESRCH (No such process)
cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
block 449287 with 157305 thanks On 2007-12-01 Andreas Metzler [EMAIL PROTECTED] wrote: [] I can reproduce this, the error is generated when killproc invokes /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5 --quiet --oknodo which is dpkg bug 157305. (I am using a block instead of reassigning, too keep the bug visible in exim.) cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
severity 449287 important thanks I've been seeing the same issue for some time on several systems, therefore raising priority. Here's the debug (set -x) output for the stop command during shutdown. Hope it helps. At first glance, the problem seems to be that first 'killproc' is being called and later also start-stop-daemon. And then later there also a 'kill -0'... Cheers, FJP Stopping MTA: + ps alx + grep '[e]xim' 5 100 2121 1 20 0 5848 912 - Ss ? 0:00 /usr/sbin/exim4 -bd -q30m 0 0 2269 20 0 2808 1368 - R? 0:00 /bin/sh /etc/rc0.d/K20exim4 stop + stop_exim + '[' -f /var/run/exim4/eximqr.pid ']' + '[' -f /var/run/exim4/exim.pid ']' + killproc -p /var/run/exim4/exim.pid /usr/sbin/exim4 + local pidfile sig status base i name_param + pidfile= + name_param= + OPTIND=1 + getopts p: opt + case $opt in + pidfile=/var/run/exim4/exim.pid + getopts p: opt + shift 2 + base=exim4 + '[' '!' /var/run/exim4/exim.pid ']' ++ echo ++ sed -e 's/^-\(.*\)/\1/' + sig= ++ echo ++ sed -e 's/^SIG\(.*\)/\1/' + sig= + '[' -n '' ']' + /sbin/start-stop-daemon --stop --pidfile /var/run/exim4/exim.pid --retry 5 --quiet --oknodo /sbin/start-stop-daemon: warning: failed to kill 2121: No such process + status=0 + '[' 0 = 1 ']' + '[' -z '' ']' + pidofproc -p /var/run/exim4/exim.pid /usr/sbin/exim4 + local pidfile line i pids= status specified pid + pidfile= + specified= + OPTIND=1 + getopts p: opt + case $opt in + pidfile=/var/run/exim4/exim.pid + specified=1 + getopts p: opt + shift 2 + '[' -z /var/run/exim4/exim.pid ']' + '[' -f /var/run/exim4/exim.pid ']' + read pid + '[' -n 2121 ']' ++ kill -0 2121 + return 1 + rm -f /var/run/exim4/exim.pid + return 0 + log_progress_msg exim4_listener + '[' -z exim4_listener ']' + echo -n ' exim4_listener' exim4_listener+ log_end_msg 0 + '[' -z 0 ']' + log_use_fancy_output + TPUT=/usr/bin/tput + EXPR=/usr/bin/expr + '[' xlinux '!=' xdumb ']' + '[' -x /usr/bin/tput ']' + '[' -x /usr/bin/expr ']' + /usr/bin/tput hpa 60 + /usr/bin/tput setaf 1 + '[' -z ']' + FANCYTTY=1 + case $FANCYTTY in + true ++ /usr/bin/tput setaf 1 + RED='' ++ /usr/bin/tput op + NORMAL='' + '[' 0 -eq 0 ']' + echo . . + return 0 + warn_paniclog + '[' -s /var/log/exim4/paniclog ']' signature.asc Description: This is a digitally signed message part.
Bug#449287: /etc/init.d/exim4 gives no such process error when stopping exim4
Package: exim4 Version: 4.68-1 Severity: normal Here is the testcase: kev1:/home/kevin# ps aux | grep exim4 102 26121 0.0 0.1 5880 920 ?Ss 18:45 0:00 /usr/sbin/exim4 -bd -q30m root 26348 0.0 0.1 3572 788 pts/6S+ 18:45 0:00 grep exim4 kev1:/home/kevin# invoke-rc.d exim4 status checking separate queue runner daemon...done (not running). checking combined SMTP listener and queue runner daemon...done (running). kev1:/home/kevin# invoke-rc.d exim4 stop Stopping MTA:/sbin/start-stop-daemon: warning: failed to kill 26121: No such process exim4_listener. kev1:/home/kevin# ps aux | grep exim4 root 26639 0.0 0.1 3572 788 pts/6S+ 18:45 0:00 grep exim4 So it appears there's something wrong with initscript/PID file handling. -- Package-specific info: Exim version 4.68 #1 built 07-Oct-2007 22:03:11 Copyright (c) University of Cambridge 2006 Berkeley DB: Berkeley DB 4.6.19: (August 10, 2007) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to replace # the DEBCONFsomethingDEBCONF strings in the configuration template files. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='smarthost' dc_other_hostnames='' dc_local_interfaces='127.0.0.1' dc_readhost='kev1.homeip.net' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='smtp.gmail.com' CFILEMODE='644' dc_use_split_config='true' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' mailname:kev1.homeip.net -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.23-rc9 (SMP w/2 CPU cores; PREEMPT) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Shell: /bin/sh linked to /bin/bash Versions of packages exim4 depends on: ii debconf [debconf-2.0] 1.5.16 Debian configuration management sy ii exim4-base4.68-1 support files for all Exim MTA (v4 ii exim4-daemon-light4.68-1 lightweight Exim MTA (v4) daemon exim4 recommends no packages. -- debconf information: * exim4/drec: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
