Bug#62358, Bug#71631)
* Upstream: Doesn't re-set log-level if not requested (closes:
Bug#76170, Bug#76170, Bug#85289)
* Upstream: Ignore zero bytes (closes: Bug#85478, Bug#85478, Bug#41068)
* Upstream: Corrected documentation for `-s' (closes: Bug#87020)
* Upstream: test for existence of syslogd-listfiles before calling
them. This got lost due to 1.4.0 brokennes which was packaged and
removed some hours later (closes: Bug#84872, Bug#66712)
* Applied patch by Tommi Virtanen <tv@debian.org> splitting the package
into `sysklogd' and `klogd' (closes:Bug#35586, Bug#72043, Bug#74864,
Bug#72122)
* Provide / depend on virtual packages system-log-daemon
and linux-kernel-log-daemon (closes: Bug#67604)
* Applied patch from Tim Janik <timj@gtk.org> to support `-s pattern' in
syslogd-listfiles
* Transition to FHS, i.e. /usr/share/doc instead of /usr/doc and
/usr/share/man instead of /usr/man (closes: Bug#79250, Bug#80771)
* Use --exec for stopping services (closes: Bug#76757)
* Corrected broken character in klogd.8 (cloes: Bug#75932)
* Only rotate logfiles with size greater than zero. This got lost due
to 1.4.0 brokennes which was packaged and removed some hours later
(closes: Bug#74993, Bug#49824)
* Added another note about modificability of cronjobs (closes:
Bug#88741)
* Since klogd replaces parts of sysklogd a proper Replaces line is there
* Added final newline to CHANGES
. Changed SOCK_STREAM to SOCK_DGRAM in syslog.c
. klogd will only change the console log level if `-c' is supplied
. syslogd.c by Bill Nottingham <notting@redhat.com>
Um, if the directory is invalid, the bind() call in
create_unix_socket fails. Without the return -1, we return the
invalid fd that we just closed. When syslogd then starts
listening, select goes into a hard loop getting EBADF, IIRC.
. klogd.c by Troels Walsted Hansen <troels@thule.no>
I found a bug in the sysklogd package version 1.4. When it
encounters a zero byte in the kernel logging output, the text
parser enters a busy loop. I came upon it when the 3c59x driver
from kernel 2.4.0 started outputting two zero bytes for the product
code of my laptop's 3Com card. It could be argued that the kernel
should never output zero bytes in the logging info, but obviously
that will happen from time to time.
I fear this bug might be considered a security issue as well, if
the kernel can be coerced to output a zero byte somehow, all kernel
logging will stop.
Wolfgang Oertl <Wolfgang.Oertl@uibk.ac.at> had a similar bugfix
idea
. klogd.c by Thomas Roessler <roessler@does-not-exist.org>
Additionally, the patch prevents LogLine from being invoked with a
negative counter as an argument.
. Keith Owens <kaos@ocs.com.au>
- Fixed bug that caused klogd to die if there is no sym_array available.
- When symbols are expanded, print the line twice. Once with
addresses converted to symbols, once with the raw text. Allows
external programs such as ksymoops do their own processing on the
original data.
* Changed Greg's e-mail address to represent his current one.
* Shortened line length for kernel logging slightly.
* Corrected return value of AddModule (closes: Bug#30093)
* Finally fixed an error with `-a' processing, thanks to Topi Miettinen
<tom@medialab.sonera.net> (closes: Bug#30462)
special messages from 2.1.78. Thanks to Chu-yeon Park
<kokids@doit.ajou.ac.kr> for informing me.
* Fixed bug that caused klogd to die if there is no System.map
available.
* Added -x switch to omit EIP translation and System.map evaluation.
Thanks to Florian La Roche <florian@knorke.saar.de>.
* Fixed small bugs in F_FORW_UNKN meachanism. Thanks to Torsten Neumann
<torsten@londo.rhein-main.de> for pointing me to it.
* Fixed problem with klogd not being able to be built on a kernel newer
than 2.1.18. Worked in a patch from Alessandro Suardi <asuardi@uninetcom.it>
