From: Llfrg@aol.com
To: florian.zimmermann@gmx.net
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Problem with the /proc filesystem
Date: Wed, 17 Mar 2004 14:16:19 -0500 [thread overview]
Message-ID: <00CBF511.1BEE7B5E.0000FADF@aol.com> (raw)
Yes, I see the same behavior using watch. Does anyone else confirms that bug? It seems to happen when idle time is zero, or close to zero, try running a "cpu consuming" process and 'watch'. I'll have my program to consider cpu idle time equals to 0 on that case.
I am using:
Linux version 2.4.18-24.7.x (bhcompile@sylvester.devel.redhat.com) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-112)) #1 Fri Jan 31 07:06:03 EST 2003
Thanks.
Leonardo
Em um e-mail de Qua, 17 Mar 2004 1:57:21 PM Hora Padrão da Costa Leste, Florian Zimmermann <florian.zimmermann@gmx.net> escreveu:
>you can test the same by using 'watch', e.g.
># watch -n1 cat /proc/stat
>
>if the errors occurs as well with 'watch' it is likely
>that the proc kernel interface is buggy.
>otherwise you should post your own code here to analyse
>whats wrong.
>
>Florian
>
>On Wed, 2004-03-17 at 19:02, Llfrg@aol.com wrote:
>> Hello,
>>
>> I am reading the first line of /proc/stat once per second. Sometimes a bug seems to occur, which is the value of the cpu idle time become lower than the cpu idle time collected one second earlier. Does anyone know what may be happening? Below is the output of my program. Idle means the last cpu idle time read from /proc/stat and old_id is the previous cpu idle time read.
>>
>> Thanks
>>
>> ###Program output:
>>
>> Idle: 210097666 old_id: 210097666
>> user: 100 nice: 0 system: 3 idle: 0 total: 103
>>
>> Idle: 210097666 old_id: 210097666
>> user: 101 nice: 0 system: 2 idle: 0 total: 103
>>
>> Idle: 210097666 old_id: 210097666
>> user: 78 nice: 0 system: 25 idle: 0 total: 103
>>
>> Idle: 210097667 old_id: 210097666
>> user: 97 nice: 0 system: 6 idle: 1 total: 104
>>
>> Idle: 210097666 old_id: 210097667
>> user: 102 nice: 0 system: 2 idle: 4294967295 total: 103
>> BUUUUG
>>
>> Idle: 210097666 old_id: 210097666
>> user: 101 nice: 0 system: 2 idle: 0 total: 103
>>
>> Idle: 210097667 old_id: 210097666
>> user: 101 nice: 0 system: 2 idle: 1 total: 104
>>
>> Idle: 210097666 old_id: 210097667
>> user: 101 nice: 0 system: 3 idle: 4294967295 total: 103
>> BUUUUG
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2004-03-17 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 19:16 Llfrg [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-17 18:02 Problem with the /proc filesystem Llfrg
2004-03-17 18:57 ` Florian Zimmermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00CBF511.1BEE7B5E.0000FADF@aol.com \
--to=llfrg@aol.com \
--cc=florian.zimmermann@gmx.net \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).