Your message dated Fri, 08 Jul 2005 17:23:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Not a bug
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 6 Jul 2005 20:34:56 +0000
>From [EMAIL PROTECTED] Wed Jul 06 13:34:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from www.treesign.com [217.17.192.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DqGba-0005k4-00; Wed, 06 Jul 2005 13:34:50 -0700
Received: from strider.tquas.lab (p213.54.159.51.tisdip.tiscali.de
[213.54.159.51])
(authenticated)
by www.treesign.com (8.11.6/8.11.6) with ESMTP id j66KYix32763;
Wed, 6 Jul 2005 22:34:44 +0200
Received: from tom by strider.tquas.lab with local (Exim 3.36 #1 (Debian))
id 1DqGbO-0002Jl-00; Wed, 06 Jul 2005 22:34:38 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Thomas Quas <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: fetchmail: daemon mode does not recognize new network connections
X-Mailer: reportbug 3.12
Date: Wed, 06 Jul 2005 22:34:38 +0200
Message-Id: <[EMAIL PROTECTED]>
Sender: Thomas Quas <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-4.3 required=4.0 tests=BAYES_00,FORGED_YAHOO_RCVD,
HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: fetchmail
Version: 6.2.5-12
Severity: normal
I typically start a network connection after the boot sequence of my laptop
finished, meaning only the loopback device is available while the system
starts fetchmail in daemon mode.
After that, I manually bring up a network connection. Unfortunately, fetchmail
daemon does not recognize the newly available connection to the internet and
keeps telling me that it awakened/went to sleep. After restart
(/etc/init.d/fetchmail restart), fetchmail starts polling messages from my
mail server.
I'd expect fetchmail to automatically recognize available connections instead
of having to restart it.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages fetchmail depends on:
ii adduser 3.63 Add and remove users and groups
ii base-files 3.1.4 Debian base system miscellaneous f
ii debconf 1.4.51 Debian configuration management sy
ii debianutils 2.13.2 Miscellaneous utilities specific t
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
-- no debconf information
---------------------------------------
Received: (at 317178-done) by bugs.debian.org; 8 Jul 2005 15:23:29 +0000
>From [EMAIL PROTECTED] Fri Jul 08 08:23:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from x095.decis.nl (aglu.demon.nl) [130.161.177.95]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DquhN-0002Gi-00; Fri, 08 Jul 2005 08:23:29 -0700
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1])
by aglu.demon.nl (Postfix) with ESMTP id 4ED53401B6
for <[EMAIL PROTECTED]>; Fri, 8 Jul 2005 17:23:02 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Fri, 08 Jul 2005 17:23:01 +0200
From: Thomas Hood <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: Not a bug
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
>
>
>I typically start a network connection after the boot sequence of my laptop
>finished, meaning only the loopback device is available while the system
>starts fetchmail in daemon mode.
>
>After that, I manually bring up a network connection. Unfortunately, fetchmail
>daemon does not recognize the newly available connection to the internet and
>keeps telling me that it awakened/went to sleep. After restart
>(/etc/init.d/fetchmail restart), fetchmail starts polling messages from my
>mail server.
>
>I'd expect fetchmail to automatically recognize available connections instead
>of having to restart it.
>
The solution is to install resolvconf.
Nico Golde wrote:
>in my opinion it is not a fetchmail bug.
Right, it isn't a fetchmail bug.
>it doesn't make sense to start it without internet
>connection.
>
>
>why do you don't start it automatically with a script with
>starting the link?
>for example if you map snort to eth0 and eth0 isn't there it
>doesn't work too.
>
>
Well, there is not much point in fetchmail's continuing to check for
mail when lo is the only network interface available. However, stopping
fetchmail during those periods when all destinations are unreachable is
difficult to implement and risks making the service less reliable.
It costs very few CPU cycles to leave fetchmail running. The only
problem is the messages in the syslog. The way to fix that is to modify
fetchmail so that it does not print those messages.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
