> - 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
** Changed in: systemd (Ubuntu Xenial)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537211
Title:
clean up /var/log/udev.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1537211/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
