Re: [gentoo-user] Re: Reduce granularity of emerge-fetch.log?
Hello, On Fri, 08 Mar 2019, Neil Bothwick wrote: >On Thu, 7 Mar 2019 17:52:08 -0600, Dale wrote: >> >> It seems you can change the output of wget with the --progress >> >> option, which you would set in FETCHCOMMAND in make.conf. >> > Doh! I thought that the output format looked familiar: I didn't >> > realize it was using wget. Thanks... >> >> Would you mind posting a example of yours? I'd like to change mine as >> well. Just need something to give me ideas and should be able to go >> from there. > >You can see the default setting with > >emerge --info -v | grep FETCHCOMMAND= > >Paste this into make.conf and fiddle with the progress settings. You can also use /var/tmp/portage/.wgetrc (see: getent passwd portage | cut -d: -f6): # grep progress /var/tmp/portage/.wgetrc progress=bar:force:noscroll showprogress=on # FETCHCOMMAND is not set by me. HTH, -dnh -- If breathing required conscious thought, the world population would be on a sharp decline.-- Greg Andrews
Re: [gentoo-user] Re: Reduce granularity of emerge-fetch.log?
On Thu, 7 Mar 2019 17:52:08 -0600, Dale wrote: > >> It seems you can change the output of wget with the --progress > >> option, which you would set in FETCHCOMMAND in make.conf. > > Doh! I thought that the output format looked familiar: I didn't > > realize it was using wget. Thanks... > > > > > Would you mind posting a example of yours? I'd like to change mine as > well. Just need something to give me ideas and should be able to go > from there. You can see the default setting with emerge --info -v | grep FETCHCOMMAND= Paste this into make.conf and fiddle with the progress settings. -- Neil Bothwick Are Cheerios really doughnut seeds? pgpcEDljxIh9n.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: Reduce granularity of emerge-fetch.log?
Grant Edwards wrote: > On 2019-03-07, Neil Bothwick wrote: >> On Thu, 7 Mar 2019 20:01:46 - (UTC), Grant Edwards wrote: >> >>> I've noticed that when downloading large files, emerge seems to write >>> an excessive number of lines to /var/log/emerge-fetch.log. The last >>> time I looked, it was writing 30-40 lines/second while downloading. >>> >>> Is there any way to reduce that to a saner number? I don't really see >>> the point of updating the log more than once every few seconds. >> It seems you can change the output of wget with the --progress option, >> which you would set in FETCHCOMMAND in make.conf. > Doh! I thought that the output format looked familiar: I didn't > realize it was using wget. Thanks... > Would you mind posting a example of yours? I'd like to change mine as well. Just need something to give me ideas and should be able to go from there. Dale :-) :-)
[gentoo-user] Re: Reduce granularity of emerge-fetch.log?
On 2019-03-07, Neil Bothwick wrote: > On Thu, 7 Mar 2019 20:01:46 - (UTC), Grant Edwards wrote: > >> I've noticed that when downloading large files, emerge seems to write >> an excessive number of lines to /var/log/emerge-fetch.log. The last >> time I looked, it was writing 30-40 lines/second while downloading. >> >> Is there any way to reduce that to a saner number? I don't really see >> the point of updating the log more than once every few seconds. > > It seems you can change the output of wget with the --progress option, > which you would set in FETCHCOMMAND in make.conf. Doh! I thought that the output format looked familiar: I didn't realize it was using wget. Thanks... -- Grant
