Comment 4 for bug 1537211
Revision history for this message
| Martin Pitt (pitti) wrote Re: move to systemd has regressed /var/log/udev.log | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> - there are various apport hooks that attach /var/log/udev to bug reports,
If it's only that, I'm happy to fix those. In fact I noticed that it was still attached by apport's attach_hardware() hookutils, I removed that. The other call that I see on my system is in libmtp, I just uploaded a fix. I'm happy to do an archive grep to update the other apport hooks.
This log does not really give you that much -- if a value is wrong or a device is missing, then you still need to boot with "debug" to get all the "why"s, like the corresponding kernel messages or the output/error messages of udev probes. You can maybe compare the order in which devices are detected in a successful and a failed boot, but for this again you need to do multiple boots and then can also just use "debug".
So I still consider it as something which is unnecessarily done at every boot and not useful enough to be kept (I look at a lot of boot failures, and haven't met a single case where this was useful..) So if you don't mind, I'd rather repurpose this as
- Search/fix remaining apport hooks which write this file
- Clean up /var/log/udev on upgrade