Comment 22 for bug 1579580

Be aware the messages will come back next time you boot after
upgrading a package that touches something in /etc, which will trigger
another scan by ureadahead. Better is the workaround I gave back in
#9, but really what I recommend is just purge ureadahead. ureadahead
only ever can help the second (and subsequent) time one boots after
updating the system, and these days I never reboot unless I have
updated, since suspend works for desktops/laptops and who reboots
servers if you don't have to?

Rich
On Sat, Sep 22, 2018 at 8:54 AM Anders Hall <email address hidden> wrote:
>
> Thanks, workaround in #19 seem to have removed (thousands of) these
> messages.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1579580
>
> Title:
> ureadahead reports relative path errors in journalctl output
>
> Status in ureadahead package in Ubuntu:
> Confirmed
>
> Bug description:
> ureadahead reports relative path errors in my journalctl output.
>
> This is currently 4368 lines of useless annoyances in my logs.
>
> To see if you have this problem, run: journalctl -b | grep ureadahead
> | grep relative | wc -l
>
> Thanks
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: ureadahead 0.100.0-19
> ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
> Uname: Linux 4.4.0-22-generic x86_64
> NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
> ApportVersion: 2.20.1-0ubuntu2
> Architecture: amd64
> Date: Sun May 8 15:55:18 2016
> InstallationDate: Installed on 2016-04-04 (34 days ago)
> InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325)
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: ureadahead
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions