All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marco d'Itri" <md@Linux.IT>
To: linux-hotplug@vger.kernel.org
Subject: [ben@callahans.org: Bug#221739: /etc/hotplug/usb.agent generates 100s of lines of error output]
Date: Thu, 04 Dec 2003 10:43:08 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-107053730019909@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 61 bytes --]

Debian bug report.

-- 
ciao, |
Marco | [3453 fu5T9iT/VZLEk]

[-- Attachment #2: Type: message/rfc822, Size: 4653 bytes --]

From: root <ben@callahans.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#221739: /etc/hotplug/usb.agent generates 100s of lines of error output
Date: Wed, 19 Nov 2003 16:06:50 -0500
Message-ID: <E1AMZXG-0000SW-00@callahans.org>

Package: hotplug
Version: 0.0.20031008-1
Severity: normal


If there's an unparseable line in /lib/modules/modules.usbmap, usb.agent
generates hundreds (in my case, over 600) lines of output during the
boot; specifically, it repeatedly prints out the environment, which
includes all the functions it has just loaded.

Easy fix: change this:

--------------------------------------------------------
    while read line
    do
        # comments are lines that start with "#" ...
        # be careful, they still get parsed by bash!
        case "$line" in
        \#*) continue ;;
        esac
--------------------------------------------------------

to this:

--------------------------------------------------------
    while read line
    do
        # comments are lines that start with "#" ...
        # be careful, they still get parsed by bash!
        case "$line" in
        \#*) continue ;;
        "") continue ;;
        esac
--------------------------------------------------------

(note the added line in the case statement.) It might also be a good
idea to count the lines in modules.usbmap and report the one that fails
to parse... I still have to hunt down which one it is. :)


Regards,
Ben Okopnik
-=-=-=-=-=-

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux Fenrir.Thor 2.4.22 #5 Wed Nov 19 15:20:15 EST 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages hotplug depends on:
ii  debconf                    1.3.15        Debian configuration management sy
ii  module-init-tools          0.9.15-pre2-2 tools for managing Linux kernel mo
ii  modutils                   2.4.25-1      Linux module utilities
ii  procps                     1:3.1.12-1    The /proc file system utilities

-- debconf information:
* hotplug/usb_keyboard: 
  hotplug/x11_usbmice_hack: false
* hotplug/static_module_list: usb-uhci
* hotplug/usbd_enable: true



             reply	other threads:[~2003-12-04 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 10:43 Marco d'Itri [this message]
2003-12-10  1:07 ` [ben@callahans.org: Bug#221739: /etc/hotplug/usb.agent generates 100s of lines of error output] Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-107053730019909@msgid-missing \
    --to=md@linux.it \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.