Re: update process
On Sun, Jan 24, 2021, at 8:56 AM, Robert McBroom via users wrote:
Lately have been seeing messages in the terminal as dnf update is
running. Example:
Warning: The unit file, source configuration file or drop-ins of
kdump.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
Reboot will do take care of that.
/usr/lib/tmpfiles.d/kdm.conf:1: Line references path below legacy
directory /var/run/, updating /var/run/kdm/ → /run/kdm/; please update
the tmpfiles.d/ drop-in file accordingly.
/usr/lib/tmpfiles.d/kdm.conf:2: Line references path below legacy
directory /var/run/, updating /var/run/xdmctl → /run/xdmctl; please
update the tmpfiles.d/ drop-in file accordingly.
Are these changes made on a reboot? Such messages are not seen if
dnfdragora is used. They can be swept away in a long update if not
beeing actively watched. How are they supposed to be handled?
In my/most? case(s) you can ignore that:
cd /var/
ls -la |grep run
lrwxrwxrwx. 1 root root 11 Aug 10 2013 lock ->
../run/lock
lrwxrwxrwx. 1 root root 6 Aug 10 2013 run -> ../run
So you see that /var/run is just a symlink to /run and thus you don't need to worry if
the config file has the legacy "/var/run" in it.
--
Doug Herr
fedoraproject.org(a)wombatz.com