From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [OFFTOPIC] udev question
Date: Sat, 18 Jun 2005 09:11:14 +0000 [thread overview]
Message-ID: <20050618091114.GA30128@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0506181213560.27030@www.buraphalinux.org>
On Sat, Jun 18, 2005 at 04:01:28PM +0700, John Gatewood Ham wrote:
> Is there some kind of 'trace' mode I can turn on that shows
> how udev makes the decisions?
Sure, do:
make clean all DEBUG=true
make install
and set udev_log="debug" in /etc/udev/udev.conf
If you call udevstart on bootup, which is normally the one that creates
/dev/null, you need to pass invoke it with:
UDEV_LOG=8 /sbin/udevstart
cause it does not follow the settings of the config, cause it may take
minutes for it to finish cause of a slow syslog...
You can also simply do (with the DEBUG compiled in):
ACTIONd DEVPATH=/class/mem/zero UDEV_LOG=8 /sbin/udev mem
and watch syslog to see what your rule does.
Kay
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-06-18 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 5:18 [OFFTOPIC] udev question John Gatewood Ham
2005-06-18 8:24 ` Kay Sievers
2005-06-18 8:55 ` John Gatewood Ham
2005-06-18 9:11 ` Kay Sievers [this message]
2005-06-19 5:17 ` 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=20050618091114.GA30128@vrfy.org \
--to=kay.sievers@vrfy.org \
--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.