Package: bluez-utils
Version: 3.30-3
Severity: minor
Tags: patch

Having enabled dund in the /etc/default/bluetooth file the startup log
message prints pand as the name of the daemon being started which is
slighly confusing, all the more so if pand is also enabled in which case
the log message suggests it is started twice whereas it is actually one
pand and one dund.

The corresponding thing also happens at shutdown.

This appears to be a typo or copy/paste error in /etc/init.d/bluetooth and
the attached patch should fix it.

Regards,
Steve.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25.7-ecrins
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bluez-utils depends on:
ii  dbus                         1.2.1-2     simple interprocess messaging syst
ii  libbluetooth2                3.35-1      Library to use the BlueZ Linux Blu
ii  libc6                        2.7-10      GNU C Library: Shared libraries
ii  libdbus-1-3                  1.2.1-2     simple interprocess messaging syst
ii  libglib2.0-0                 2.16.3-2    The GLib library of C routines
ii  libusb-0.1-4                 2:0.1.12-12 userspace USB programming library
ii  lsb-base                     3.2-12      Linux Standard Base 3.2 init scrip
ii  makedev                      2.3.1-88    creates device files in /dev
ii  module-init-tools            3.4-1       tools for managing Linux kernel mo
ii  udev                         0.114-2     /dev/ and hotplug management daemo

Versions of packages bluez-utils recommends:
ii  bluez-audio                   3.30-3     Bluetooth audio support

-- no debconf information
--- etc/init.d/bluetooth.orig   2008-04-17 17:42:38.000000000 +0100
+++ etc/init.d/bluetooth        2008-07-14 19:22:54.000000000 +0100
@@ -127,7 +127,7 @@
 {
        if test "$DUND_ENABLED" != "0"; then
                start-stop-daemon --start --quiet --exec $DUND_DAEMON -- 
$DUND_OPTIONS
-               [ "$VERBOSE" != no ] && log_progress_msg "pand"
+               [ "$VERBOSE" != no ] && log_progress_msg "dund"
 
        fi
        if test "$PAND_ENABLED" != "0"; then
@@ -141,7 +141,7 @@
 {
        if test "$DUND_ENABLED" != "0"; then
                start-stop-daemon --stop --quiet --exec $DUND_DAEMON || true
-               [ "$VERBOSE" != no ] && log_progress_msg "pand"
+               [ "$VERBOSE" != no ] && log_progress_msg "dund"
        fi
        if test "$PAND_ENABLED" != "0"; then
                start-stop-daemon --stop --quiet --exec $PAND_DAEMON || true

Reply via email to