Debian bug report logs - #1695
sysklogd problems

Message received at debian-bugs:

From olis.north.de!indrom!joey Wed Nov  1 01:09:14 1995
Return-Path: <indrom!joey@olis.north.de>
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
Subject: Re: Bug#1695

reassign

Message received at debian-bugs-done:

From olis.north.de!indrom!joey Fri Oct 20 08:11:47 1995
Return-Path: <indrom!joey@olis.north.de>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t6J6o-000B6bC; Fri, 20 Oct 95 08:11 PDT
Received: from gimli.Informatik.Uni-Oldenburg.DE by pixar.com with SMTP id AA24352
  (5.67b/IDA-1.5 for debian-bugs-done-pipe@mongo.pixar.com); Fri, 20 Oct 1995 08:11:07 -0700
Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1)
	id <m0t6HPX-00003ZC>; Fri, 20 Oct 95 14:22 CET
Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13)
	id <m0t6Ff9-0005WjC@olis.north.de>; Fri, 20 Oct 95 12:30 MEZ
Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey)
	by finlandia.Infodrom.North.DE from joey (Martin Schulze) 
	id m0t6E1w-000K0ZC; Fri, 20 Oct 95 10:46 MET
Message-Id: <m0t6E1w-000K0ZC@finlandia.Infodrom.North.DE>
From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Subject: Bug#1695: sysklogd problems
To: debian-bugs-done@Pixar.com
Date: Fri, 20 Oct 1995 10:46:24 +0100 (MET)
X-Href: http://home.pages.de/~joey/
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 928       

Hallo Ian Murdock!

}Package: sysklogd
}Version: 1.2
}Package_Revision: 12

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

The whole stuff is obsolete when I upload it in the next days. So I
mark it as done.

ChangeLog:

Fri Oct 20 10:40:55 1995 Martin Schulze  <joey@finlandia.infodrom.north.de>

	* changed a typo in syslog.conf (thanks to Bernd S. Brentrup)

	* changed the startup message (Bug#1695)

	* changed the name in control file (Bug#1695)

	* changed the order for stopping (Bug#1695)


Regards,

	Joey


-- 
   / Martin Schulze  *  joey@infodrom.north.de  *  26129 Oldenburg /
  / +49-441-777884  *  Login&Passwd: nuucp  *  Index: ~/ls-lR.gz  /
 /                                     http://home.pages.de/~joey/
/ Linux - the choice of a GNU generation                        /
----------------------------------------------------------------
30.10.95: Oldenburger Linux-Stammtisch, ab 20h im DaCapo

Message received at debian-bugs:

From chiark.chu.cam.ac.uk!ian Tue Oct 17 18:04:58 1995
Return-Path: <ian@chiark.chu.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t5MwD-0006DqC; Tue, 17 Oct 95 18:04 PDT
Received: from artemis.chu.cam.ac.uk by pixar.com with SMTP id AA14634
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Tue, 17 Oct 1995 18:04:31 -0700
Received: from chiark.chu.cam.ac.uk by artemis.chu.cam.ac.uk with smtp
	(Smail3.1.29.1 #33) id m0t5NyM-0007u9C; Wed, 18 Oct 95 02:11 GMT
Received: by chiark.chu.cam.ac.uk
	id m0t5Mvx-0002abC
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 18 Oct 95 02:04 BST
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
Subject: Re: Bug#1695: sysklogd problems

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 received at debian-bugs:

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.