Re: page fault degaradation performance

On 11/6/07, binto [EMAIL PROTECTED] wrote: I just wanna know, how to reduce the number of page faults to upgrade program or OS performance? is there any parameters that i must set if i reduce the number of page fault? Don't forget that some amount of page faults are normal consequences of

Re: page fault degaradation performance

* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: how to reduce the number of page faults to upgrade program or OS performance? Install more memory. I can cause paging on my hugely overendowed RELENG_6 system (8GB, ~2GB active) just by reading some big files and churning through cache. It's

FreeBSD 6.2 Crash

Hi all FreeBSD Hackers! :) My FreeBSD auto reboot itself and I got this report by kgdb, but actually I'm not a programmer. I don't know how to debug this error. Could someone helps with fixing? Thanx in advanced! FreeBSD .com 6.2-RELEASE-p8 FreeBSD 6.2-RELEASE-p8 #0: Tue Oct 30 22:54:18 EET

Re: pkg_add doesn't keep dependent pkgs

On Tue, Nov 06, 2007 at 12:27:13PM -0800, Maslan wrote: Package dependencies may change, depending on the user settings and port maintainers configuration for the port (i.e. Makefiles). The same sort of applies to packages as well. Or were you referring to just packages instead of

Re: FreeBSD 6.2 Crash

Atanas Gendov wrote: Hi all FreeBSD Hackers! :) My FreeBSD auto reboot itself and I got this report by kgdb, but actually I'm not a programmer. I don't know how to debug this error. Could someone helps with fixing? Thanx in advanced! FreeBSD .com 6.2-RELEASE-p8 FreeBSD 6.2-RELEASE-p8 #0:

where did the peak mbuf stat go ?

FreeBSD 4.x, netstat -m: 70/4336/26624 mbufs in use (current/peak/max) Never any doubt - if peak=max, I hit the limit. Super useful. Furthermore, by watching the peak I can see when I am getting close, rather than waiting for denied requests to pile up after the fact. FreeBSD 6.x, netstat -m:

A TrustedBSD voluntary sandbox policy.

I'm considering developing a policy/module for TrustedBSD loosely based on the systrace concept - A process loads a policy and then executes another program in a sandbox with fine grained control over what that program can do. I'm aiming for a much simpler implementation, however. No interaction.