From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: udev not running new rules
Date: Sun, 12 Aug 2007 14:10:11 +0000 [thread overview]
Message-ID: <20070812141011.GA20093@bongo.bofh.it> (raw)
In-Reply-To: <1186927115.3225.10.camel@tigger>
[-- Attachment #1.1: Type: text/plain, Size: 321 bytes --]
On Aug 12, Peter Gordon <peter@pg-consultants.com> wrote:
> Killing udev and restarting doesn't help.
I just do not believe this.
> It seems that udev firstly checks which files exist. How can I get the new rule set to be run as soon as it is created?
No, it does not. Do not use a symlink.
--
ciao,
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 226 bytes --]
_______________________________________________
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:[~2007-08-12 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 13:58 udev not running new rules Peter Gordon
2007-08-12 14:10 ` Marco d'Itri [this message]
2007-08-12 14:19 ` Kay Sievers
2007-08-12 19:03 ` Peter Gordon
2007-08-12 19:28 ` Kay Sievers
2007-08-12 19:39 ` Peter Gordon
2007-08-13 7:06 ` Gerald V. Livingston II
2007-08-13 11:09 ` Bryan Kadzban
2007-08-13 11:38 ` Kay Sievers
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=20070812141011.GA20093@bongo.bofh.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).