Your message dated Mon, 28 Nov 2005 00:57:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#340565: quagga: Repeat of #315467: So-called "fix" doesn't 
resolve the actual problem.
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; 24 Nov 2005 08:28:55 +0000
>From [EMAIL PROTECTED] Thu Nov 24 00:28:55 2005
Return-path: <[EMAIL PROTECTED]>
Received: from hiryuu.systemec.nl ([194.229.164.250] ident=postfix)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1EfCTP-0001eg-7h
        for [EMAIL PROTECTED]; Thu, 24 Nov 2005 00:28:55 -0800
Received: by hiryuu.systemec.nl (Postfix, from userid 1000)
        id CBE50415351; Thu, 24 Nov 2005 09:28:52 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Rens Houben <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: quagga: Repeat of #315467: So-called "fix" doesn't resolve the actual
 problem.
X-Mailer: reportbug 3.17
Date: Thu, 24 Nov 2005 09:28:52 +0100
Message-Id: <[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-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: quagga
Version: 0.99.2-1
Severity: grave
Tags: patch
Justification: causes non-serious data loss


The problem described in #315467 (all negotiated routes get dropped
during a restart of quagga) is in fact *not* due to the "simple concept
of a daemon restarting" as you implied -- in fact, the quagga authors
already thought long and hard about that possible issue and allowed for
it: When starting any of the quagga daemons with the --retain flag, that
daemon will not flush its routes when exiting.

The *real* cause of the problem is the explicit route flush you added in
the /etc/init.d/quagga script at the "stop" case. It's not only
unneccessary (because each daemon can be configured via
/etc/quagga/debian.conf to either flush or retain its routes), it's
dangerous.

Removing line 225 and 226 from /etc/init.d/quagga fixes the problem
without requiring a debconf prompt not to restart quagga ever.

-- System Information:
Debian Release: testing/unstable
  APT prefers stable
  APT policy: (900, 'stable'), (100, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages quagga depends on:
ii  adduser                       3.79       Add and remove users and groups
ii  debconf [debconf-2.0]         1.4.59     Debian configuration management sy
ii  iproute                       20041019-4 Professional tools to control the 
ii  libc6                         2.3.5-8    GNU C Library: Shared libraries an
ii  libcap1                       1:1.10-14  support for getting/setting POSIX.
ii  libncurses5                   5.5-1      Shared libraries for terminal hand
ii  libpam0g                      0.79-3     Pluggable Authentication Modules l
ii  libreadline5                  5.0-11     GNU readline and history libraries
ii  logrotate                     3.7.1-2    Log rotation utility

quagga recommends no packages.

-- debconf information:
* quagga/really_stop: true

---------------------------------------
Received: (at 340565-done) by bugs.debian.org; 27 Nov 2005 23:57:52 +0000
>From [EMAIL PROTECTED] Sun Nov 27 15:57:52 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail3b.westend.com ([212.117.79.78] helo=mail3b2.westend.com)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1EgWP1-0005vI-UA
        for [EMAIL PROTECTED]; Sun, 27 Nov 2005 15:57:52 -0800
Received: from localhost (localhost [127.0.0.1])
        by mail3b2.westend.com (Postfix) with ESMTP id 1F39012127D;
        Mon, 28 Nov 2005 00:57:51 +0100 (CET)
Received: from mail3b2.westend.com ([127.0.0.1])
        by localhost (mail3b [127.0.0.1]) (amavisd-new, port 20024)
        with ESMTP id 02365-05; Mon, 28 Nov 2005 00:57:48 +0100 (CET)
Received: from app109.intern (gate.lathspell.de [212.117.68.82])
        by mail3b2.westend.com (Postfix) with ESMTP id E67DA121279;
        Mon, 28 Nov 2005 00:57:47 +0100 (CET)
Date: Mon, 28 Nov 2005 00:57:47 +0100
From: Christian Hammers <[EMAIL PROTECTED]>
To: Rens Houben <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#340565: quagga: Repeat of #315467: So-called "fix" doesn't
 resolve the actual problem.
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
X-Mailer: Sylpheed-Claws 1.0.5 (GTK+ 1.2.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Hello Rens

I've just replied you in bug report #315467, please keep the discussion
there. I close this as dublicate.

bye,

-christian-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to