Your message dated Thu, 10 Sep 2009 23:27:06 +0200
with message-id <[email protected]>
and subject line Re: Bug#540523: sysv-rc: bogus message on runlevel switch
has caused the Debian Bug report #540523,
regarding sysv-rc: bogus message on runlevel switch
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
540523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540523
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.87dsf-2
Severity: normal
switching runlevel (here from 3 to 2) produces on my cosole the message
/etc/init.d/rc: line 318: [: /etc/rc3.d/S26network-manager: binary
operator expected
the line in question reads
[ -f $previous_start ] && [ ! -f $stop ] && continue
i have no idea, what that means, except maybe the hphen in
network-manager?
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29.4 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages sysv-rc depends on:
ii insserv 1.12.0-10 boot sequence organizer using LSB
ii sysvinit-utils 2.87dsf-2 System-V-like utilities
Versions of packages sysv-rc recommends:
ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip
Versions of packages sysv-rc suggests:
pn bum <none> (no description available)
ii sysv-rc-conf 0.99-6 SysV init runlevel configuration t
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 2.87dsf-2
[Arne Anka]
>> The error you saw is not present in this log,
>
> yes, i wondered, too.
OK. Unless you can provide information on how to reproduce the
problem, or more details, I guess the problem was elsewhere, and
solved there too.
Because of this, I close this report. Feel free to reopen if you have
more information.
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
