I just realized, that when I am running xosview, I really don't give
a rats you-know-what about the memory part of that thing anyway, I
am more interested in the CPU meters mainly. I could certainly whip
us up a non-memory-status version if anyone is interested... that
would 'raise the impedence' a whole lot, and stop it from being so
intrusive unless there is another one of those 'hits' somewhere else
in /proc...
Robert Hyatt Computer and Information Sciences
[EMAIL PROTECTED] University of Alabama at Birmingham
(205) 934-2213 115A Campbell Hall, UAB Station
(205) 934-5473 FAX Birmingham, AL 35294-1170
On Mon, 8 Feb 1999, Robert M. Hyatt wrote:
> On 8 Feb 1999, Mike Romberg wrote:
>
> > >>>>> " " == Robert M Hyatt <[EMAIL PROTECTED]> writes:
> >
> > > It is probably 'xosview' itself...
> >
> > Yea. As MOLNAR Ingo pointed out in this thread, there is a pretty
> > big hit when xosview reads the proc filesystem for memory stats. This
> > is why it only attempts to do this once a second or so. So, xosview
> > is in effect watching it's own contibution to the processor state.
> >
> > When xosview is not visible or iconified, it suspends reading from
> > the proc filesystem and the blips should not be there. Of course, you
> > wont be able to see this with xosview :).
> >
> > Mike Romberg ([EMAIL PROTECTED])
> >
> >
>
>
> I'd call this a "low-impedence probe" if you know what I mean.
>
> :)
>
>
>
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
