Subject: Bug#3769: problems with sysklogd postinst

From: Richard Kettlewell <[email-masked]>
Date: Sat, 13 Jul 96 23:09:02 +0100 (BST)

Package: sysklogd
Version: 1.3-6

    richard@sfere:binary$ really dpkg -i base/sysklogd-1.3-6.deb 
    Selecting previously deselected package sysklogd.
[......omissions........]
    Installing new version of config file /etc/cron.weekly/sysklogd ...
    Version 1.3 of the package is the culmination of about two years of
    experience and bug reports on the 1.2 version from both the INTERNET
    and our corporate Linux networks.
    
    The default behaviour of syslogd has altered from 1.2 to 1.3. By default
    *no* messages from the UDP port are accepted.
    
    Read the documentation in /usr/doc/base/sysklogd carefully. Some important
    things have been changed!
    starting /sbin/syslogd ...
    starting /sbin/klogd ...
    klogd: Already running.
    
    richard@sfere:binary$ ps uxaw | head -1 ; ps uxaw | grep log
    USER       PID %CPU %MEM  SIZE   RSS TTY STAT START   TIME COMMAND
    richard   8418  0.0  1.1   912   368  p5 S    22:58   0:00 grep log 
    root       100  0.0  1.1   816   372  ?  S    18:04   0:00 /sbin/klogd 
    root       217  0.0  5.1  2640  1592  ?  S    18:05   0:02 xterm -ls +ut -geometry 80x24+0-0 -title sfere -n login 
    root      8390  0.0  1.3   848   424  ?  S    22:51   0:00 /sbin/syslogd 

You need to killall klogd as well as syslogd.

    richard@sfere:binary$ ls /etc/rc4.d/
    K11cron@         S19bind@         S20syslogd@      S89cron@
    S10sysklogd@     S20diald@        S25netstd_nfs@   S99xdm@
    S15netstd_init@  S20lpd@          S30netstd_misc@  S99xfs@
    S18netbase@      S20smtpd@        S35inn@
    richard@sfere:binary$ 

The symlinks in /etc/rc?.d/ are still there.  The postinst contains an
attempt to remove them, but it doesn't work.

Additionally the postinst should also be modified to conform with the
guidelines, in particular with respect to this paragraph:

       If a package has a vitally important piece of information to
    pass to the user (such as "don't run me as I am, you must edit the
    following configuration files first or you risk your system
    emitting badly-formatted messages"), it should display this in the
    `postinst' script and prompt the user to hit Return to acknowledge
    the message.  Copyright messages do not count as vitally important
    (they belong in `/usr/doc/copyright'; neither do instructions on
    how to use a program (these should be in on line documentation,
    where all the users can see them).

I should have imagined that the advert about the years of development
etc can safely be ommitted, in particular - it's better suited to
static documentation than an installation message.

-- 
Richard Kettlewell   [email-masked]   [email-masked]
                             http://www.elmail.co.uk/staff/richard/