On 07/25/2017 02:34 PM, Cristian Sava wrote:
> I'm not sure. I tried many times and it did not stop in ~10 min, so no.
Thinking a little bit more about it It may not be odd in some cases that it
takes more than 10 minutes. The process will also download the packages that
are to
be updated
On Tue, 25 Jul 2017 14:26:04 +0800
Ed Greshko wrote:
> If you find yourself catching the update time too often for your
> liking you can "systemctl disable dnf-makecache.timer".
I wasn't aware of this, so glad to learn of it, but have been doing the
same thing by putting
metadata_timer_sync=0
in
On 07/25/2017 02:34 PM, Cristian Sava wrote:
> 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:
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;
On 07/25/2017 02:04 PM, Cristian Sava wrote:
> Trying to update F26 systems:
>
> [root@localhost ~]# dnf update
> Waiting for process with pid 28949 to finish.
> ^CKeyboardInterrupt: Terminated.
> [root@localhost ~]# ps aux | grep dnf
> root 7724 0.0 0.0 10824 884 pts/0S+ 08:48 0:
Trying to update F26 systems:
[root@localhost ~]# dnf update
Waiting for process with pid 28949 to finish.
^CKeyboardInterrupt: Terminated.
[root@localhost ~]# ps aux | grep dnf
root 7724 0.0 0.0 10824 884 pts/0S+ 08:48 0:00 grep
--color=auto dnf
root 28949 0.0 0.5 391816 4
