public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Miell <nmiell@attbi.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Davide Libenzi <davidel@xmailserver.org>,
	"Kuppuswamy,
	" Priyadarshini <Priyadarshini.Kuppuswamy@compaq.com>,
	linux-kernel@vger.kernel.org
Subject: Re: system call for finding the number of cpus??
Date: 08 Apr 2002 18:12:41 -0700	[thread overview]
Message-ID: <1018314763.1714.4.camel@entropy> (raw)
In-Reply-To: <20020408215814.GC13043@werewolf.able.es>

On Mon, 2002-04-08 at 14:58, J.A. Magallon wrote:
> >sysconf(_SC_NPROCESSORS_CONF);
> >
> 
> I din't really trusted you, so digged inside includes till bits/confname.h
> Why the h*ll the manpage about sysconf does not talk about that ?????
> 

For some odd reason, the FSF doesn't like man pages. If you read the
info documentation for glibc, you'll find the _SC_NPROCESSORS_CONF
property listed in the "libc : System Configuration : Sysconf :
Constants for Sysconf" page. The man pages tend to lag behind the actual
info documentation, because they are maintained seperately.


  parent reply	other threads:[~2002-04-09  1:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 21:18 system call for finding the number of cpus?? Kuppuswamy, Priyadarshini
2002-04-08 21:25 ` Robert Love
2002-04-08 21:27   ` Christoph Hellwig
2002-04-08 21:37     ` Mark Hahn
2002-04-08 22:02       ` Dr. David Alan Gilbert
2002-04-11 10:11         ` Rusty Russell
2002-04-08 21:58     ` H. Peter Anvin
2002-04-09 14:28       ` Vince Weaver
2002-04-08 21:51   ` J.A. Magallon
2002-04-08 22:59   ` David Ford
2002-04-08 21:56 ` Davide Libenzi
2002-04-08 21:58   ` J.A. Magallon
2002-04-08 22:08     ` Davide Libenzi
2002-04-09  1:12     ` Nicholas Miell [this message]
2002-04-09 15:37 ` Tigran Aivazian
  -- strict thread matches above, loose matches on Subject: below --
2002-04-08 21:54 Kuppuswamy, Priyadarshini
2002-04-08 22:05 ` Davide Libenzi
2002-04-08 22:12 ` J.A. Magallon
2002-04-09  5:36   ` Bernd Eckenfels
2002-04-09 15:39 ` Tigran Aivazian

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=1018314763.1714.4.camel@entropy \
    --to=nmiell@attbi.com \
    --cc=Priyadarshini.Kuppuswamy@compaq.com \
    --cc=davidel@xmailserver.org \
    --cc=jamagallon@able.es \
    --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