Bug 139124

Summary:	add way to renice a running emerge -- portage niceness
Product:	Portage Development	Reporter:	Aaron Peterson <alpeterson>
Component:	Enhancement/Feature Requests	Assignee:	Portage team <dev-portage>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	High
Version:	2.1
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	184128

Description Aaron Peterson 2006-07-03 23:55:45 UTC

I ran top and tried to renice the running emerge command.

as I suspected, the child processes stayed "nice"

I wanted them to be mean dang it!

and I didn't want to have to restart the emerge because I was so long into it....

I could just renice everything else on the system to the same level of niceness... but that's getting silly.

Comment 1 Marius Mauch (RETIRED) gentoo-dev

2006-07-04 05:40:05 UTC

IMO this is way beyond the scope of portage, shuold rather be a separate tool that can renices any process tree.

Comment 2 Aaron Peterson 2006-07-04 18:23:18 UTC

I tried using the separate tool !!

top could not renice it....

emerge spawns new processes at a nice level specified in make.conf

I suggest that portage checks it's own nice level, and spans new processes at it's own level  rather than some configuration value.

We would then be ABLE to renice portage.

Comment 3 Marius Mauch (RETIRED) gentoo-dev

2006-07-05 03:42:09 UTC

Ah, your inital comment didn't make it clear you were talking about new subprocesses.

Comment 4 Aaron Peterson 2006-07-05 09:52:29 UTC

ok... I thought it was obvious 

and I see how it's not.

And I agree that it would be way beyond the scope to catch keyclicks or whatever to renice it...

Comment 5 Marius Mauch (RETIRED) gentoo-dev

2007-07-09 05:23:19 UTC

Took another look at it today, and AFAICT it works as it should.