Mailing List Archive: exim: users

exim 4.63 SMTP listener keeping log file open for days

Index | Next | Previous | View Threaded

mh+exim-users at zugschlus

May 2, 2008, 2:26 AM

Post #1 of 10 (550 views)
Permalink

exim 4.63 SMTP listener keeping log file open for days

Hi,

one Debian exim user reports (see http://bugs.debian.org/476958) that
his exim SMTP listener process (the one running with -bd -q30m) keeps
/var/log/exim/mainlog open for days after log rotation:

|# ps auxww | grep [4]349
|102 4349 0.0 0.2 11756 2884 ? Ss Apr26 0:01 /usr/sbin/exim4 -bd -q30m
|# lsof -p 4349
|COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
|[snippage]
|exim4 4349 Debian-exim 6w REG 3,5 184728 128 /var/log/exim4/mainlog.1 (deleted)

Since Debian rotates mainlog daily, this means that the file wasn't
closed for at least more than 24 hours, after /var/log/exim4/mainlog
was rotated to /var/log/exim4/mainlog.1 and, the day later, was
compressed to /var/log/exim4/mainlog.2.gz and deleted.

I have never seen this happen on any of my own systems, and Debian has
been shipping this setup of exim 4.63 as part of our default install
in the stable distribution for more than a year.

I therefore strongly suspect that this is a local issue on the system
of the bug reporter, but since exim is documented to close the log
immediately after writing to it, which situation could lead to the log
kept open for this excessive amount of time?

Greetings
Marc

--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

dot at dotat

May 2, 2008, 4:26 AM

Post #2 of 10 (531 views)
Permalink

Re: exim 4.63 SMTP listener keeping log file open for days [In reply to]

On Fri, 2 May 2008, Marc Haber wrote:
>
> one Debian exim user reports (see http://bugs.debian.org/476958) that
> his exim SMTP listener process (the one running with -bd -q30m) keeps
> /var/log/exim/mainlog open for days after log rotation:
>
> |# ps auxww | grep [4]349
> |102 4349 0.0 0.2 11756 2884 ? Ss Apr26 0:01 /usr/sbin/exim4 -bd -q30m
> |# lsof -p 4349
> |COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
> |[snippage]
> |exim4 4349 Debian-exim 6w REG 3,5 184728 128 /var/log/exim4/mainlog.1 (deleted)

Is that pid actually the parent listening process? Is there proof that
that log file was rotated days ago?

> I therefore strongly suspect that this is a local issue on the system
> of the bug reporter, but since exim is documented to close the log
> immediately after writing to it, which situation could lead to the log
> kept open for this excessive amount of time?

Well the code in the daemon is careful to close the logs so I can't see
how this can happen.

Tony.
--
<fanf[at]exim.org> <dot[at]dotat.at> http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

mh+exim-users at zugschlus

May 2, 2008, 5:03 AM

Post #3 of 10 (527 views)
Permalink

Re: exim 4.63 SMTP listener keeping log file open for days [In reply to]

On Fri, 2 May 2008 12:26:35 +0100, Tony Finch <dot[at]dotat.at> wrote:
>On Fri, 2 May 2008, Marc Haber wrote:
>> one Debian exim user reports (see http://bugs.debian.org/476958) that
>> his exim SMTP listener process (the one running with -bd -q30m) keeps
>> /var/log/exim/mainlog open for days after log rotation:
>>
>> |# ps auxww | grep [4]349
>> |102 4349 0.0 0.2 11756 2884 ? Ss Apr26 0:01 /usr/sbin/exim4 -bd -q30m
>> |# lsof -p 4349
>> |COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
>> |[snippage]
>> |exim4 4349 Debian-exim 6w REG 3,5 184728 128 /var/log/exim4/mainlog.1 (deleted)
>
>Is that pid actually the parent listening process?

How can I make the user find out? Is there any possibility that there
are more than one exim process with -bd -q30m around?

Inside the [snippage], I snipped a line saying
|exim4 4349 Debian-exim 3u IPv4 10856266 TCP *:smtp (LISTEN)
(which I had better left in).

>Is there proof that
>that log file was rotated days ago?

Other than the user claiming to not having messed with the logs, and
Debian rotating the logs on a daily basis by default, no.

>> I therefore strongly suspect that this is a local issue on the system
>> of the bug reporter, but since exim is documented to close the log
>> immediately after writing to it, which situation could lead to the log
>> kept open for this excessive amount of time?
>
>Well the code in the daemon is careful to close the logs so I can't see
>how this can happen.

A pity, I'd love to find out what happens here.

Greetings
Marc

--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

dot at dotat

May 2, 2008, 8:06 AM

Post #4 of 10 (528 views)
Permalink

Re: exim 4.63 SMTP listener keeping log file open for days [In reply to]

On Fri, 2 May 2008, Marc Haber wrote:
> On Fri, 2 May 2008 12:26:35 +0100, Tony Finch <dot[at]dotat.at> wrote:
> >
> >Is that pid actually the parent listening process?
>
> How can I make the user find out?

Check its ppid or run exiwhat (though it it's wedged the latter won't work).

> Is there any possibility that there are more than one exim process with
> -bd -q30m around?

Yes, all the connection-handling processes have the same proctitle as the
parent listener.

> Inside the [snippage], I snipped a line saying
> |exim4 4349 Debian-exim 3u IPv4 10856266 TCP *:smtp (LISTEN)

Yes I saw that in the bug report. It seems that Exim closes the listening
sockets after forking so that might be the parent process - the lack of
connected sockets suggests this, though that doesn't rule it out from
being a queue runner.

> Other than the user claiming to not having messed with the logs, and
> Debian rotating the logs on a daily basis by default, no.

Hmm, and /proc/pid/fd is no use either :-(

Well it looks like I have a live one, and it looks rather broken - some
kind of deadlock, possibly signal related? It's a bit mysterious.

COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
exim 363 exim cwd DIR 8,4 144 20 /spool/exim.in
exim 363 exim rtd DIR 8,1 4096 2 /
exim 363 exim txt REG 8,1 741641 384409 /opt/exim-4.67+ppsw+0/bin/exim
exim 363 exim mem REG 0,0 0 [heap] (stat: No such file or directory)
exim 363 exim mem REG 8,1 42109 15972 /lib/libnss_files-2.4.so
exim 363 exim mem REG 8,1 41986 15976 /lib/libnss_nis-2.4.so
exim 363 exim mem REG 8,1 21283 15970 /lib/libnss_dns-2.4.so
exim 363 exim mem REG 8,1 5260 383034 /opt/exim-4.67+ppsw+0/etc/etc.ppsw/db/server_params.cdb
exim 363 exim mem REG 8,1 85304 356218 /opt/zlib-1.2.3+0/lib/libz.so.1.2.3
exim 363 exim mem REG 8,1 13814 15961 /lib/libdl-2.4.so
exim 363 exim mem REG 8,1 1412466 15955 /lib/libc-2.4.so
exim 363 exim mem REG 8,1 1496021 370574 /opt/OpenSSL-0.9.8e+0/lib/libcrypto.so.0.9.8
exim 363 exim mem REG 8,1 291598 370570 /opt/OpenSSL-0.9.8e+0/lib/libssl.so.0.9.8
exim 363 exim mem REG 8,1 104687 15981 /lib/libpthread-2.4.so
exim 363 exim mem REG 8,1 838527 369291 /opt/db4-4.2.52+0/lib/libdb-4.2.so
exim 363 exim mem REG 8,1 180631 15963 /lib/libm-2.4.so
exim 363 exim mem REG 8,1 47259 15959 /lib/libcrypt-2.4.so
exim 363 exim mem REG 8,1 87850 15966 /lib/libnsl-2.4.so
exim 363 exim mem REG 8,1 74278 15983 /lib/libresolv-2.4.so
exim 363 exim mem REG 8,1 31943 15968 /lib/libnss_compat-2.4.so
exim 363 exim mem REG 8,1 128633 15948 /lib/ld-2.4.so
exim 363 exim 0u CHR 1,3 3661 /dev/null
exim 363 exim 1u CHR 1,3 3661 /dev/null
exim 363 exim 2u CHR 1,3 3661 /dev/null
exim 363 exim 3r REG 8,1 5260 383034 /opt/exim-4.67+ppsw+0/etc/etc.ppsw/db/server_params.cdb
exim 363 exim 6u sock 0,5 1978191144 can't identify protocol
exim 363 exim 7u sock 0,5 1978191144 can't identify protocol
exim 363 exim 8u unix 0xf7c5e3c0 1977360074 socket
exim 363 exim 9w REG 8,4 365546126 19179 /spool/exim/log/mainlog.02 (deleted)

Process 363 attached - interrupt to quit
futex(0xb7c137ec, FUTEX_WAIT, 2, NULL <unfinished ...>
Process 363 detached

(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7bbe57e in __lll_mutex_lock_wait () from /lib/libc.so.6
#2 0xb7b7292d in _L_mutex_lock_1783 () from /lib/libc.so.6
#3 0xb7ad1000 in ?? ()
#4 0xb7ba3a63 in __read_nocancel () from /lib/libc.so.6
#5 0xb7b53e38 in _IO_file_read_internal () from /lib/libc.so.6
#6 0xb7b70f7f in localtime () from /lib/libc.so.6
#7 0x080a3a59 in tod_stamp ()
#8 0x08079c16 in log_write ()
#9 0x08060085 in usr1_handler ()
#10 <signal handler called>
#11 0xffffe410 in __kernel_vsyscall ()
#12 0xb7ba2403 in __xstat64[at]GLIBC_2.1 () from /lib/libc.so.6
#13 0xb7b72e60 in __tzfile_read () from /lib/libc.so.6
#14 0xb7b71e02 in tzset_internal () from /lib/libc.so.6
#15 0xb7b7288e in tzset () from /lib/libc.so.6
#16 0xb7b76a86 in strftime_l () from /lib/libc.so.6
#17 0xb7b76926 in strftime () from /lib/libc.so.6
#18 0x00000020 in ?? ()
#19 0x080dfbbb in ?? ()
#20 0xbfd7b67c in ?? ()
#21 0xb7c123a0 in free () from /lib/libc.so.6
#22 0x00000068 in ?? ()
#23 0xbfd7b6b8 in ?? ()
#24 0x080a3cd7 in tod_stamp ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Tony.
--
<fanf[at]exim.org> <dot[at]dotat.at> http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

mh+exim-users at zugschlus

May 3, 2008, 3:36 PM

Post #5 of 10 (515 views)
Permalink

Re: exim 4.63 SMTP listener keeping log file open for days [In reply to]

On Fri, 2 May 2008 16:06:40 +0100, Tony Finch <dot[at]dotat.at> wrote:
>On Fri, 2 May 2008, Marc Haber wrote:
>> On Fri, 2 May 2008 12:26:35 +0100, Tony Finch <dot[at]dotat.at> wrote:
>> >
>> >Is that pid actually the parent listening process?
>>
>> How can I make the user find out?
>
>Check its ppid or run exiwhat (though it it's wedged the latter won't work).

Do I still have to do that while you see the issue yourself?

>> Is there any possibility that there are more than one exim process with
>> -bd -q30m around?
>
>Yes, all the connection-handling processes have the same proctitle as the
>parent listener.

I see...

>> Inside the [snippage], I snipped a line saying
>> |exim4 4349 Debian-exim 3u IPv4 10856266 TCP *:smtp (LISTEN)
>
>Yes I saw that in the bug report. It seems that Exim closes the listening
>sockets after forking so that might be the parent process - the lack of
>connected sockets suggests this, though that doesn't rule it out from
>being a queue runner.

In my experience, a queue runner shows up as "exim -q", even if
invoked from the main daemon.

>Well it looks like I have a live one, and it looks rather broken - some
>kind of deadlock, possibly signal related? It's a bit mysterious.
>
>COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
>exim 363 exim cwd DIR 8,4 144 20 /spool/exim.in
>exim 363 exim rtd DIR 8,1 4096 2 /
>exim 363 exim txt REG 8,1 741641 384409 /opt/exim-4.67+ppsw+0/bin/exim
>exim 363 exim mem REG 0,0 0 [heap] (stat: No such file or directory)
>exim 363 exim mem REG 8,1 42109 15972 /lib/libnss_files-2.4.so
>exim 363 exim mem REG 8,1 41986 15976 /lib/libnss_nis-2.4.so
>exim 363 exim mem REG 8,1 21283 15970 /lib/libnss_dns-2.4.so
>exim 363 exim mem REG 8,1 5260 383034 /opt/exim-4.67+ppsw+0/etc/etc.ppsw/db/server_params.cdb
>exim 363 exim mem REG 8,1 85304 356218 /opt/zlib-1.2.3+0/lib/libz.so.1.2.3
>exim 363 exim mem REG 8,1 13814 15961 /lib/libdl-2.4.so
>exim 363 exim mem REG 8,1 1412466 15955 /lib/libc-2.4.so
>exim 363 exim mem REG 8,1 1496021 370574 /opt/OpenSSL-0.9.8e+0/lib/libcrypto.so.0.9.8
>exim 363 exim mem REG 8,1 291598 370570 /opt/OpenSSL-0.9.8e+0/lib/libssl.so.0.9.8
>exim 363 exim mem REG 8,1 104687 15981 /lib/libpthread-2.4.so
>exim 363 exim mem REG 8,1 838527 369291 /opt/db4-4.2.52+0/lib/libdb-4.2.so
>exim 363 exim mem REG 8,1 180631 15963 /lib/libm-2.4.so
>exim 363 exim mem REG 8,1 47259 15959 /lib/libcrypt-2.4.so
>exim 363 exim mem REG 8,1 87850 15966 /lib/libnsl-2.4.so
>exim 363 exim mem REG 8,1 74278 15983 /lib/libresolv-2.4.so
>exim 363 exim mem REG 8,1 31943 15968 /lib/libnss_compat-2.4.so
>exim 363 exim mem REG 8,1 128633 15948 /lib/ld-2.4.so
>exim 363 exim 0u CHR 1,3 3661 /dev/null
>exim 363 exim 1u CHR 1,3 3661 /dev/null
>exim 363 exim 2u CHR 1,3 3661 /dev/null
>exim 363 exim 3r REG 8,1 5260 383034 /opt/exim-4.67+ppsw+0/etc/etc.ppsw/db/server_params.cdb
>exim 363 exim 6u sock 0,5 1978191144 can't identify protocol
>exim 363 exim 7u sock 0,5 1978191144 can't identify protocol
>exim 363 exim 8u unix 0xf7c5e3c0 1977360074 socket
>exim 363 exim 9w REG 8,4 365546126 19179 /spool/exim/log/mainlog.02 (deleted)

That doesn't look like a Debian system, so can I assume that you see
the issue as well and don't need any more debugging help from our
side? Or is there anything more I can do to help?

>(gdb) bt
>#0 0xffffe410 in __kernel_vsyscall ()
>#1 0xb7bbe57e in __lll_mutex_lock_wait () from /lib/libc.so.6
>#2 0xb7b7292d in _L_mutex_lock_1783 () from /lib/libc.so.6
>#3 0xb7ad1000 in ?? ()
>#4 0xb7ba3a63 in __read_nocancel () from /lib/libc.so.6
>#5 0xb7b53e38 in _IO_file_read_internal () from /lib/libc.so.6
>#6 0xb7b70f7f in localtime () from /lib/libc.so.6
>#7 0x080a3a59 in tod_stamp ()
>#8 0x08079c16 in log_write ()
>#9 0x08060085 in usr1_handler ()
>#10 <signal handler called>
>#11 0xffffe410 in __kernel_vsyscall ()
>#12 0xb7ba2403 in __xstat64[at]GLIBC_2.1 () from /lib/libc.so.6
>#13 0xb7b72e60 in __tzfile_read () from /lib/libc.so.6
>#14 0xb7b71e02 in tzset_internal () from /lib/libc.so.6
>#15 0xb7b7288e in tzset () from /lib/libc.so.6
>#16 0xb7b76a86 in strftime_l () from /lib/libc.so.6
>#17 0xb7b76926 in strftime () from /lib/libc.so.6
>#18 0x00000020 in ?? ()
>#19 0x080dfbbb in ?? ()
>#20 0xbfd7b67c in ?? ()
>#21 0xb7c123a0 in free () from /lib/libc.so.6
>#22 0x00000068 in ?? ()
>#23 0xbfd7b6b8 in ?? ()
>#24 0x080a3cd7 in tod_stamp ()
>Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Does it help to have my user run exim with debugging symbols (Which is
easily possible on Debian)?

Is it sufficient to run gdb <pid> and to type "bt"?

Greetings
Marc

--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

ssmeenk at freshdot

May 4, 2008, 6:15 AM

Post #6 of 10 (506 views)
Permalink

Re: exim 4.63 SMTP listener keeping log file open for days [In reply to]

Quoting Tony Finch (dot[at]dotat.at):

> Well it looks like I have a live one, and it looks rather broken - some
> kind of deadlock, possibly signal related? It's a bit mysterious.

I'm also seeing what Marc posted. I'm 100% certain pid 10309 is my master
process and running lsof also produces:

| exim4 10309 Debian-exim 10w REG 9,2 714262 24068181
| /var/log/exim4/mainlog.1 (deleted)

Yet, i do get correct loglines in /var/log/exim4/mainlog and the whole
system seems to function just perfectly well.

Now i wonder, does this listenerprocess log anything at all? :)
I haven't looked at the source yet, but i tend to think only the
children log to the 'current' mainlog. Also, my logrotate.d/exim4-base
does not have any postrotate script to reload the daemon...

Looks to me like some open()-call, which the master process does to see
if the logs are writeable, didn't get closed properly. Funny thing
is, when i restart Exim and check proc/pid/fd there's no logfiles.

Weird.

-Sndr.
--
| It is better to regret something you HAVE done,
| than to regret something you HAVEN'T done...
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

mh+exim-users at zugschlus

May 4, 2008, 8:53 AM

Post #7 of 10 (502 views)
Permalink

Re: exim 4.63 SMTP listener keeping log file open for days [In reply to]

On Sun, 4 May 2008 15:15:58 +0200, Sander Smeenk
<ssmeenk[at]freshdot.net> wrote:
>Now i wonder, does this listenerprocess log anything at all? :)
>I haven't looked at the source yet, but i tend to think only the
>children log to the 'current' mainlog. Also, my logrotate.d/exim4-base
>does not have any postrotate script to reload the daemon...

According to the docs, there was never a need to reload the daemon
after log rotation.

Greetings
Marc

--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

dot at dotat

May 5, 2008, 8:05 AM

Post #8 of 10 (486 views)
Permalink

Re: exim 4.63 SMTP listener keeping log file open for days [In reply to]

On Sun, 4 May 2008, Marc Haber wrote:
>
> That doesn't look like a Debian system, so can I assume that you see
> the issue as well and don't need any more debugging help from our
> side? Or is there anything more I can do to help?

Some help might be useful, in case we're seeing different problems. In my
case the wedged process with the open log file is definitely NOT the
master process.

> Does it help to have my user run exim with debugging symbols (Which is
> easily possible on Debian)?

Yes, that would be helpful, thanks.

> Is it sufficient to run gdb <pid> and to type "bt"?

Yes, though you need the -p flag to gdb.

This is going to require a wet towel around the head to stop it from
overheating...

Tony.
--
<fanf[at]exim.org> <dot[at]dotat.at> http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

mh+exim-users at zugschlus

May 22, 2008, 10:36 AM

Post #9 of 10 (351 views)
Permalink

Re: exim 4.63 SMTP listener keeping log file open for days [In reply to]

On Mon, 5 May 2008 16:05:50 +0100, Tony Finch <dot[at]dotat.at> wrote:
>On Sun, 4 May 2008, Marc Haber wrote:
>> That doesn't look like a Debian system, so can I assume that you see
>> the issue as well and don't need any more debugging help from our
>> side? Or is there anything more I can do to help?
>
>Some help might be useful, in case we're seeing different problems. In my
>case the wedged process with the open log file is definitely NOT the
>master process.

So you'd want to see the output of exiwhat?

>> Does it help to have my user run exim with debugging symbols (Which is
>> easily possible on Debian)?
>
>Yes, that would be helpful, thanks.
>
>> Is it sufficient to run gdb <pid> and to type "bt"?
>
>Yes, though you need the -p flag to gdb.

And when do you want the backtrace to be done? Wait for a wedged
process, attach to it with gdb and bt then?

>This is going to require a wet towel around the head to stop it from
>overheating...

Probably ;)

Greetings
Marc

--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

mh+exim-users at zugschlus

Jul 3, 2008, 4:06 AM

Post #10 of 10 (236 views)
Permalink

Re: exim 4.63 SMTP listener keeping log file open for days [In reply to]

On Mon, 5 May 2008 16:05:50 +0100, Tony Finch <dot[at]dotat.at> wrote:
>This is going to require a wet towel around the head to stop it from
>overheating...

Just in time for the summer, this issue is now Bugzilla #728.

Greetings
Marc

--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com