> - the --export-db output doesn't include timestamps - or even ordering
information, which may be very important for debugging.
Ah, forgot to reply to this -- there is USEC_INITIALIZED which is the
monotonic timestamp since the boot.
** Summary changed:
- move to systemd has regressed /var/log/
> - 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.
On Sun, Jan 24, 2016 at 06:38:22PM -, Martin Pitt wrote:
> I'm quite aware that we don't write this any more, but why do we
> penalize every boot with this? What is realistically there that isn't in
> "udevadm info --export-db"?
Well, it's possible I may not have known about the existence of t
I'm quite aware that we don't write this any more, but why do we
penalize every boot with this? What is realistically there that isn't in
"udevadm info --export-db"?
** Changed in: systemd (Ubuntu Xenial)
Status: New => Incomplete
--
You received this bug notification because you are a me
If we want a full log with timestamps etc. I'm fine with providing a
disabled service which does that. This could be enabled using the
standard "systemctl enable udev-monitor", or also via the kernel command
line if "debug" is given. But I am really resistant about writing this
extra log file all t
