diff options
author | kay.sievers@vrfy.org <kay.sievers@vrfy.org> | 2004-12-20 08:57:31 +0100 |
---|---|---|
committer | Greg KH <gregkh@suse.de> | 2005-04-26 23:19:09 -0700 |
commit | eabfc9736703ce0dc81b233d78821d408aa565f2 (patch) | |
tree | a34d77ab4794731cbed5212dd78c8870f33ce7e2 /udevd.c | |
parent | 9f8dfa19cfd2b502bf794f39a421cbb7c4cc0404 (diff) |
[PATCH] handle renamed network interfaces properly if we manage hotplug.d/
If we take over the hotplug call and manage the events we don't need
to call the event fake script in dev.d/. Just set all expected values
to the new network interface name and call hotplug.d/. This way the
device renaming is completely handled inside of udev and userspace
can't get confused.
Diffstat (limited to 'udevd.c')
-rw-r--r-- | udevd.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -335,7 +335,7 @@ static void handle_udevsend_msg(int sock) if (strncmp(key, "PHYSDEVPATH=", 12) == 0) msg->physdevpath = &key[12]; } - msg->envp[i++] = "MANAGED_EVENT=1"; + msg->envp[i++] = "UDEVD_EVENT=1"; msg->envp[i] = NULL; /* if no seqnum is given, we move straight to exec queue */ |