Your message dated Sun, 16 Apr 2006 21:12:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362963: udev: handling of multiple rules
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: udev
Version: 0.088-2
Severity: normal
What happens if several rules match an event? The man page seems to
say they will all apply. For example, the last paragraph of the
DESCRIPTION section refers to "Rules [plural] that match". Some of
the options refer to cutting off rules application, implying that
ordinarily they proceed.
This does not seem to be the behavior I'm getting. I put this rule
ACTION="add", SUBSYSTEM="net", RUN+="/sbin/nameif"
before the usual hotplug.rules. The ethernet device was not up at the
end of this, suggesting that the following rule (invoking net.agent)
never ran.
I changed the rule to
ACTION="add", SUBSYSTEM="net", RUN+="/sbin/nameif", RUN+="/bin/sh -c
'/lib/udev/net.agent &'"
and ran udevtrigger. This time it worked.
So either only the first rule is processed, or this is one of those
other networking bugs that have been reported where things fail on
startup but work later.
Other documentation on the internet indicates that udev stops as soon
as the first match is found, so maybe this is the actual and intended
behavior. If so, it would be good for the man page to make that
clear.
I also found the documentation on OPTIONS a little hard to follow. I
guess the intent is, e.g., OPTIONS=last_rule to apply one of these
options. I wasn't clear that OPTIONS was a key. Perhaps an example
would help, if you think others might be as dense :)
This was using a 2.6.15 kernel (I'm sending this from a different
system than the one I ran udev on).
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
On Apr 16, Ross Boylan <[EMAIL PROTECTED]> wrote:
> What happens if several rules match an event? The man page seems to
> say they will all apply.
Unsurprisingly, it's true.
> This does not seem to be the behavior I'm getting. I put this rule
> ACTION="add", SUBSYSTEM="net", RUN+="/sbin/nameif"
You cannot use nameif with udev, because udev will not know that the
interface name has changed.
Do not invent silly things, udev itself can rename network interfaces.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
