Hi

OS : ubuntu
language:C/C++


I want to get the whole contents of cpu info, throttling, battery status like information. through system calls only and have to store them in a structure.. pls dont suggest:1) reading /proc/cpuinfo 2)script program 3) system command

I want only system calls except uname();

in windows we have APIS to get all those above mentioned infos. So is there any system calls like that. pls guide me

Why not.

What is wrong with reading system info from /proc ?

The Windows way is not necessarily (nor even very often) the right way.

Part of the Unix design philosophy is to have fewer OS API's than you would find in a non Unix OS and to use the basic file I/O APIs in imaginative ways to reduce the need for other APIs.

The /proc filesystem is a logical extension of that philosophy. I think Linux has or had various APIs to get some of the same info that you can get from /proc, but using /proc is more general and more likely to be able to smoothly transition as the underlying OS features are changed or enhanced.

ya ofcourse.. I agree with u.. If we read /proc/cpuinfo, the problem is with parsing the file to get the our needed appropriate information and storing them back in a structure variables. It increases my program size. So asked. If u know the APIs please post it.

write it,
it wont take more then 5K if you do it right
hint: fscanf() and sscanf can be one of your best friend for parsing that and fgets

Is any system call to read info like /proc/cpuinfo.

Actullay i can read it through /proc/cpuinfo but the details are different at intell & PPC. So there is some portability problem of the program.

thanx

See the following pdf:
http://www.digilife.be/quickreferenc...0Reference.pdf

Thanks. I don't have time for a careful enough read to see if that has any answers to the OP's question. But slightly off topic:

Do you know of a similar document for X86_64 architecture Linux system calls?

Hi -

1. Reading from "/proc/info" is in fact, for most purposes, the ideal approach for Linux

2. Granted - "/proc/info" is not necessarily portable to other *nix systems. And certainly not portable to Windows.

The Windows equivalent is WMI ... which is 100x more verbose ... and not portable to anything outside of Windows.

3. Of course the information in "/proc/info" is different between x86 and PPC - they're different architectures!

4. The claim that parsing /proc/info would somehow make the program "bigger" in some significant way ... is just absurd.

IMHO .. PM