Debian bug report logs - #1695, boring messages

Message sent to debian-devel@pixar.com:

Subject: Bug#1695: sysklogd problems
Reply-To: Ian Murdock <imurdock@debian.org>, debian-bugs@pixar.com
Resent-From: Ian Murdock <imurdock@debian.org>
Resent-To: debian-devel@pixar.com
Resent-Date: Tue, 17 Oct 1995 16:33:01 GMT
Resent-Message-ID: <debian-bugs-handler.1695.B10171623270@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
Message-Id: <m0t5Em6-0001cOC@imagine.imaginit.com>
Date: Tue, 17 Oct 95 11:21 EST
From: Ian Murdock <imurdock@debian.org>
To: debian-bugs@pixar.com

Package: sysklogd
Version: 1.2
Package_Revision: 12

I've noticed a few problems with the new sysklogd package:

* First of all (and this is my fault--I wrote the message), the
message printed from /etc/init.d/sysklogd says "If syslogd exits with
this message".  Actually, it doesn't exit--it just displays a warning,
so this should just say "If syslogd displays this messsage".

* The name of the package appears to have been changed to "sysklogd",
but the control file still says "syslogd", and the package is still
referenced via dpkg as "syslogd".  If the package name has actually
changed, it should be changed in the control file, and it should
also declare a conflict with "syslogd".  I'm not convinced changing
the name is a good idea, but this is the correct procedure for doing
it.

* klogd and syslogd are stopped too early in the shutdown process,
before many daemons have been stopped.  As a result, daemons that
try to log messages via syslog when they exit don't get them
properly recorded.  To fix this, do the following in the postinst:

   update-rc.d sysklogd defaults 10 90 >/dev/null

* The /etc/rc?.d links didn't get properly updated when I upgraded
to the sysklogd package that changed from using level 20 to level 10.
You may have to specifically deal with this in the postinst, because
update-rc.d won't erase links that already exist.

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Ian Murdock <imurdock@debian.org>
Subject: Bug#1695: Acknowledgement (was: sysklogd problems)
In-Reply-To: <m0t5Em6-0001cOC@imagine.imaginit.com>
References: <m0t5Em6-0001cOC@imagine.imaginit.com>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1695" or "Re: Bug#1695" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

Message sent to debian-devel@pixar.com:

Subject: Bug#1695: sysklogd problems
Reply-To: Ian Jackson <ian@chiark.chu.cam.ac.uk>, debian-bugs@pixar.com
Resent-From: Ian Jackson <ian@chiark.chu.cam.ac.uk>
Resent-To: debian-devel@pixar.com
Resent-Date: Wed, 18 Oct 1995 01:18:01 GMT
Resent-Message-ID: <debian-bugs-handler.1695.B10180106010@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
Message-Id: <m0t5Mvx-0002abC@chiark.chu.cam.ac.uk>
Date: Wed, 18 Oct 95 02:04 BST
From: Ian Jackson <ian@chiark.chu.cam.ac.uk>
To: debian-bugs@Pixar.com

Ian Murdock writes ("Bug#1695: sysklogd problems"):
> [...]
> * The /etc/rc?.d links didn't get properly updated when I upgraded
> to the sysklogd package that changed from using level 20 to level 10.
> You may have to specifically deal with this in the postinst, because
> update-rc.d won't erase links that already exist.

It will do, *if* you say update-rc.d <foo> remove.  This is usually
only done in the postrm script when it is given the `purge' flag.

I think that would be unwise here; better would be something involving
for, sed and mv to rename the links.

Ian.

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Ian Jackson <ian@chiark.chu.cam.ac.uk>
Subject: Bug#1695: Info received (was Bug#1695: sysklogd problems)
In-Reply-To: <m0t5Mvx-0002abC@chiark.chu.cam.ac.uk>
References: <m0t5Mvx-0002abC@chiark.chu.cam.ac.uk>

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developers to
accompany the original report.

If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#1695" or "Re: Bug#1695" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: joey@finlandia.Infodrom.North.DE (Martin Schulze)
In-Reply-To: <m0t6E1w-000K0ZC@finlandia.Infodrom.North.DE>
References: <m0t6E1w-000K0ZC@finlandia.Infodrom.North.DE> <m0t5Em6-0001cOC@imagine.imaginit.com>
Subject: Bug#1695: marked as done (was: sysklogd problems)

Your message dated Fri, 20 Oct 1995 10:46:24 +0100 (MET)
with message-id <m0t6E1w-000K0ZC@finlandia.Infodrom.North.DE>
and subject line Bug#1695: sysklogd problems
has caused the attached bug report to be marked as done.

It is your now responsibility to ensure that the bug report is dealt
with.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Ian Jackson
(maintainer, debian-bugs)

Received: with rfc822 via encapsulated-mail; Tue, 17 Oct 1995 16:23:25 GMT
From debian.org!imurdock Tue Oct 17 09:19:03 1995
Return-Path: <imurdock@debian.org>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t5EjH-000AMzC; Tue, 17 Oct 95 09:19 PDT
Received: from imagine.imaginit.com by pixar.com with SMTP id AA03032
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Tue, 17 Oct 1995 09:18:37 -0700
Received: by imagine.imaginit.com
	id <m0t5Em6-0001cOC@imagine.imaginit.com>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Tue, 17 Oct 95 11:21 EST
Message-Id: <m0t5Em6-0001cOC@imagine.imaginit.com>
Date: Tue, 17 Oct 95 11:21 EST
From: Ian Murdock <imurdock@debian.org>
To: debian-bugs@pixar.com
Subject: sysklogd problems

Package: sysklogd
Version: 1.2
Package_Revision: 12

I've noticed a few problems with the new sysklogd package:

* First of all (and this is my fault--I wrote the message), the
message printed from /etc/init.d/sysklogd says "If syslogd exits with
this message".  Actually, it doesn't exit--it just displays a warning,
so this should just say "If syslogd displays this messsage".

* The name of the package appears to have been changed to "sysklogd",
but the control file still says "syslogd", and the package is still
referenced via dpkg as "syslogd".  If the package name has actually
changed, it should be changed in the control file, and it should
also declare a conflict with "syslogd".  I'm not convinced changing
the name is a good idea, but this is the correct procedure for doing
it.

* klogd and syslogd are stopped too early in the shutdown process,
before many daemons have been stopped.  As a result, daemons that
try to log messages via syslog when they exit don't get them
properly recorded.  To fix this, do the following in the postinst:

   update-rc.d sysklogd defaults 10 90 >/dev/null

* The /etc/rc?.d links didn't get properly updated when I upgraded
to the sysklogd package that changed from using level 20 to level 10.
You may have to specifically deal with this in the postinst, because
update-rc.d won't erase links that already exist.

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Ian Murdock <imurdock@debian.org>
Subject: Bug#1695 acknowledged by developer (was: sysklogd problems)
References: <m0t6E1w-000K0ZC@finlandia.Infodrom.North.DE> <m0t5Em6-0001cOC@imagine.imaginit.com>
In-Reply-To: <m0t5Em6-0001cOC@imagine.imaginit.com>

This is an automatic notification regarding your bug report.

Responsibility for it has been taken by one of the developers, namely
joey@finlandia.Infodrom.North.DE (Martin Schulze).

You should be hearing from them with a substantive response shortly, if
you have not already done so.  If not, please contact them directly,
or email debian-bugs@pixar.com or myself.

Ian Jackson
(maintainer, debian-bugs)

Message sent to debian-devel@pixar.com:

Subject: Bug#1695: 
Reply-To: joey@finlandia.Infodrom.North.DE (Martin Schulze), debian-bugs@pixar.com
Resent-From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Resent-To: debian-devel@pixar.com
Resent-Date: Wed, 01 Nov 1995 09:18:01 GMT
Resent-Message-ID: <debian-bugs-handler.1695.B11010910410@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: sysklogd
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Wed, 01 Nov 1995 09:18:01 GMT
Received: with rfc822 via encapsulated-mail; Wed, 01 Nov 1995 09:10:39 GMT
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0tAZAS-0004AEC; Wed, 1 Nov 95 01:09 PST
Received: from gimli.Informatik.Uni-Oldenburg.DE by pixar.com with SMTP id AA06499
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Wed, 1 Nov 1995 01:08:30 -0800
Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1)
	id <m0tAOkp-0000rdC>; Tue, 31 Oct 95 23:01 CET
Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13)
	id <m0tAOhw-0005Q9C@olis.north.de>; Tue, 31 Oct 95 22:59 MEZ
Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey)
	by finlandia.Infodrom.North.DE from joey (Martin Schulze)
	id m0tANkv-000K4OC; Tue, 31 Oct 95 21:58 MET
Message-Id: <m0tANkv-000K4OC@finlandia.Infodrom.North.DE>
Date: Tue, 31 Oct 95 21:58 MET
From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
To: debian-bugs@pixar.com

reassign

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Subject: Bug#1695: Info received (was Bug#1695)
In-Reply-To: <m0tANkv-000K4OC@finlandia.Infodrom.North.DE>
References: <m0tANkv-000K4OC@finlandia.Infodrom.North.DE>

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developers to
accompany the original report.

If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#1695" or "Re: Bug#1695" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

Ian Jackson / iwj10@thor.cam.ac.uk, with the debian-bugs tracking mechanism

This page last modified 09:43:02 GMT Wed 01 Nov