Re: Run away CPU FreeBSD 4.9 Release #0
> > What's the actual problem? Are important programs failing to get cycles? > > I don't know the reason for the issue, but I too have had many problems > with screen. (4.8 or 4.9 box?) It works, it just uses up all the CPU > available. (Starting at 0.x percent going up to 100 percent) The fix was > to build the screen port, and the problem(s) went away. So, again, why is this a problem? screen is only taking those CPU cycles when nothing else wants them, right? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Run away CPU FreeBSD 4.9 Release #0
[snip] > > Some processes run away with the CPU. Screen is one of the worst offenders > > along with python.. > > The CPU starts out at about 15% and slowly ramps up to 100%. > > As the % ramps up, the priority increases up to about 60 > > If more than one screen is launched, then the will share the CPU but the > > priority still sits about 60. [..] > What's the actual problem? Are important programs failing to get cycles? I don't know the reason for the issue, but I too have had many problems with screen. (4.8 or 4.9 box?) It works, it just uses up all the CPU available. (Starting at 0.x percent going up to 100 percent) The fix was to build the screen port, and the problem(s) went away. I don't remember specifically on which releases this issue occurs, I do know that it's been more than just a single one. I've had the same issue on several different systems as well. Just build screen from ports and the issue will go away. I haven't (directly) used python before, but it's always been built from ports as a dependency of another port. That might have something to do with it. -Wolfe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Run away CPU FreeBSD 4.9 Release #0
"Matt Villion" <[EMAIL PROTECTED]> writes: > I have just installed 4.9 R0 on to new hardware and have encountered an > unusual issue. > It was not detected straight away as everything appeared to do what it was > supposed to do... > > Some processes run away with the CPU. Screen is one of the worst offenders > along with python.. > The CPU starts out at about 15% and slowly ramps up to 100%. > As the % ramps up, the priority increases up to about 60 > If more than one screen is launched, then the will share the CPU but the > priority still sits about 60. > > Any ideas what this could be and how to fix. What's the actual problem? Are important programs failing to get cycles? -- Lowell Gilbert, embedded/networking software engineer, Boston area: resume/CV at http://be-well.ilk.org:8088/~lowell/resume/ username/password "public" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Run away CPU FreeBSD 4.9 Release #0
Greetings, I have just installed 4.9 R0 on to new hardware and have encountered an unusual issue. It was not detected straight away as everything appeared to do what it was supposed to do... Some processes run away with the CPU. Screen is one of the worst offenders along with python.. The CPU starts out at about 15% and slowly ramps up to 100%. As the % ramps up, the priority increases up to about 60 If more than one screen is launched, then the will share the CPU but the priority still sits about 60. Any ideas what this could be and how to fix. Matt Villion ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"