Todd Zullinger wrote: > Mark Haney wrote: >> Yep, starting udev backup fixed it. > > > It doesn't happen often and I've yet to look much at bugzilla to see > if someone else has reported this. I didn't think I had enough info > to file a bug about it. But considering that it clearly happens to > more people than just me, it might be a good idea to see if it's been > reported and report it if not. The maintainer may well have better > ideas for how to debug it and catch what's caused it to die. > > A quick search in bugzilla doesn't lead me to anything obvious, but > there are 47 bugs found for the udev package with udevd in the > comments and I haven't done anything more than peruse the summaries. > Would you have time to peak at some of them and file a bug if none > cover the case of it just dying? If you do, let me know and I'll add > a note confirming that it happens for me sometimes too. :) > > Well, I just dug through my logs and all I see if an instance where udev was updated (July 6th in my case and I do updates on my systems about every day) and it looked like it tried to restart and failed to bind to the address since it was already in use. I don't see where it actually failed, but that's the only entry in my log files since I did the upgrade. Do you see anything similar in your logs? -- Recedite, plebes! Gero rem imperialem! Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
