Le 06.03.2008 14:23:46, Marc Haber a écrit :
>On Thu, Mar 06, 2008 at 01:57:03PM +0100, Jean-Luc Coulon (f5ibh)
>wrote:
>> I've the same error message.
>
>Please copy and paste from a shell and show exactly how you reproduce
>the issue.

I get the following error.

[EMAIL PROTECTED] % sudo /etc/init.d/exim4 stop
Stopping MTA:/sbin/start-stop-daemon: signal value must be numeric or 
name of signal (KILL, INT, ...)
Try /sbin/start-stop-daemon --help for more information.

>
>> I saw that /etc/init.d/exim4 calls "killproc" to stop the daemon 
>> (killproc -p $PID $DAEMON).
>
>Yes, that's mandated by the LSB,
>
>>  However killproc is not (no more available) in sid.
>
>Eh?
>
>$ grep killproc /lib/lsb/init-functions
>killproc () {
>$ dpkg --search /lib/lsb/init-functions
>lsb-base: /lib/lsb/init-functions

Same here.

>$ apt-cache policy lsb-base
>lsb-base:
>  Installed: 3.2-3
>  Candidate: 3.2-3
>  Version table:
> *** 3.2-3 0
>        500 http://debian.debian.zugschlus.de sid/main Packages
>        100 /var/lib/dpkg/status
>     3.1-24 0
>        -10 http://debian.debian.zugschlus.de lenny/main Packages
>     3.1-23.2etch1 0
>        -10 http://debian.debian.zugschlus.de etch/main Packages


[EMAIL PROTECTED] % apt-cache policy lsb-base
lsb-base:
  Installé : 3.2-2
  Candidat : 3.2-4
 Table de version :
     3.2-4 0
        500 ftp://ftp.fr.debian.org sid/main Packages
 *** 3.2-2 0
        100 /var/lib/dpkg/status

>
>Explain why killproc is no longer available in sid.

Well. I've got the same symtoms with cpufreqd few days ago and IIRC, 
the message explicitly mentionned killproc.
As there have been many lsb update past few days (I just remarked I'm 
late also), I wanted to make a supposition it is related to killproc (I 
missed the ?, sorry).

Regards

Jean-Luc

Attachment: pgpA9Pvw1iEI6.pgp
Description: PGP signature

Reply via email to