Bug 451104
Summary: | udev restart causes loss of access to pseudo terminals and eth interface loses IP address | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kent Baxley <kbaxley> |
Component: | udev | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | woodard |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-20 11:30:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kent Baxley
2008-06-12 19:30:04 UTC
You are _not_ supposed to run start_udev on a fully booted system :) You may want "udevadm trigger" or "udevtrigger" followed by "udevsettle". For the selinux messages, open a bug against selinux-policy or kbd. $ rpm -qf /bin/loadkeys kbd-1.12-31.fc9.i386 Ok. I've finally had a chance to go back and try the commands you suggested instead of start_udev, and, although I'm not losing my IP Address information, I am still losing control over my pseudo terminals. If I run udevadm trigger or udevtrigger, the terminals (e.g. konsole, gnome-terminal) will go unresponsive after issuing either command. The udev version I'm now running is: udev-124-1.fc9.2 Running udevtrigger on an older release like RHEL5 does not reproduce this sort of behavior. Also, is there any documentation anywhere on the proper way to restart udev, if start_udev is not recommended? Thanks. # man udevadm |