On Tue, 2017-07-25 at 14:26 +0800, Ed Greshko wrote: ... > Had you not killed it, you would have seen something like this.... > > [egreshko@acer ~]$ systemctl status dnf-makecache.timer > ● dnf-makecache.timer - dnf makecache timer > Loaded: loaded (/usr/lib/systemd/system/dnf-makecache.timer; > enabled; vendor pre > Active: active (waiting) since Sun 2017-07-23 19:37:39 CST; 1 day > 18h ago > > Jul 23 19:37:39 acer.greshko.com systemd[1]: Started dnf makecache > timer. > > Basically, about once/hour dnf will check and will update its cache > if needed. See > the man page for dnf and search for makecache for the details. > > > 2) WHY DNF does not ever stop and must be killed to update the > > system? > > You just happened to catch it in the middle of trying to update the > cache. Had you > simply waited a bit more your first dnf would have proceeded. > I'm not sure. I tried many times and it did not stop in ~10 min, so no. > > > > > That is seen on many F26 boxes (new installs or upgrades). > > > > If you find yourself catching the update time too often for your > liking you can > "systemctl disable dnf-makecache.timer". > Thanks for the tip, but do not expect everyone to know/do this. Cristian Sava _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
