R0b0t1 wrote: > On Fri, Jul 6, 2018 at 2:16 PM, Dale <rdalek1...@gmail.com> wrote: >> Grant Edwards wrote: >>> Now that the public key stuff is working again (knock on wood), I'm >>> curious if it's usual for an emerge --sync to take 10-15 minutes >>> longer than it used due to the "Verifying /usr/portage" step. >>> >>> On some systems (with fewer packages installed) it only takes a minute >>> or less. But, on my "main" desktop system it takes 10-15 minutes every >>> time. During the verify step, the emerge process is only using about >>> 5% of the CPU, and my system is running 80% or more idle. >>> >> >> I haven't timed mine yet but that sounds about like mine here. I'm not >> sure what the bottleneck is but I have a four core AMD CPU running at >> 3.2GHz with 16GBs of ram and SATA spinning rust drives. While I'm glad >> to have the added security measures, it does add a significant amount of >> time to the update process, the tree not the compile part. We all know >> the compile part can get big. lol >> >> I guess like everything else, we'll just have to get used to it. People >> will hack a ham sandwich if they can and can get something from it. >> That would be mustard on mine. Some may like Mayo, which is fine too. >> ;-) >> > Run a program with `strace -c` to get statistics on time spent in > system calls. It will be disk IO. > >
I was thinking my drive light was on a lot during that time but wasn't sure. I used to go to the kitchen and get something to drink and a snack and it be ready when I came back. I guess now I can cook a light meal and come back and it be ready. Maybe I will lose a few pounds because of this, looking for something positive in this besides the obvious security improvements. :? Either way, it takes longer but given the status of hackers, we really need this. It seems github sort of shined a light on what can happen even if it is noticed pretty quick. Dale :-) :-)
