mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-x features ?
Date: Tue, 16 Jan 2001 23:18:57 +0100	[thread overview]
Message-ID: <3A64C8D1.4C0C0456@wanadoo.fr> (raw)
In-Reply-To: <200101151959.f0FJxDB248265@saturn.cs.uml.edu>

"Albert D. Cahalan" wrote:
> 
> Pierre Rousselet writes:
> 
> > 1) top (procps-2.0.7) gives me the messages :
> > 'bad data in /proc/uptime'
> > 'bad data in /proc/loadavg'
> > cat /proc/uptime
> > 1435.30 904.74
> > cat /proc/loadavg
> > 0.01 0.21 0.29 1/17 19444
> > What is wrong ?
> 
> Which 2.4.0-x kernel, and how was procps compiled?
> (the broken gcc again perhaps?)
> 
> You might as well get procps-010114.tar.gz (new just yesterday!) and
> compile it yourself. The top command seems to tolerate Red Hat's
> fixed gcc, which you should get if you are using Red Hat 7.

I did that. Compilation OK with gcc-2.95.2 top still doesn't work (
top > /dev/null tells you 'bad data in ...' just before the screen
blanks).
logout after commenting LC_ALL=fr and LANG=fr in /etc/profile 
login again : top works. 

It is a question of '.' and ','


------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2001-01-16 22:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15  5:19 Pierre Rousselet
2001-01-15 19:59 ` Albert D. Cahalan
2001-01-16 13:14   ` John Fremlin
2001-01-16 21:50     ` Pierre Rousselet
2001-01-16 22:18   ` Pierre Rousselet [this message]

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=3A64C8D1.4C0C0456@wanadoo.fr \
    --to=pierre.rousselet@wanadoo.fr \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®