touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #131003
[Bug 1537211] Re: move to systemd has regressed /var/log/udev.log
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 member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1537211
Title:
move to systemd has regressed /var/log/udev.log
Status in systemd package in Ubuntu:
Incomplete
Status in systemd source package in Xenial:
Incomplete
Bug description:
The udev package contains an upstart job, /etc/init/udevmonitor.conf,
whose purpose is to record boot-time information about devices in a
log file for future debugging. There is no equivalent systemd unit
for this job, so with the move to systemd, we now lose this useful
debugging information. I'm not aware of any other way under systemd
to get a replay of the boot-time kernel events. If there is one,
that's fine, but otherwise there should be a systemd unit equivalent
here that can give us this log.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1537211/+subscriptions
References