Programming

I'm trying to write a C program to view server statistics such as:
- server general information
- CPU usage
- memory usage
- running processes

Cany anybody gives me hints on those system calls ??


ps: I'm using Tru64 unix

Dont know about tru64 unix

but if I had to do it, I would do one of the following

1. Read the information from the /proc files
2. find the man pages of the commands corresponding to the system call

eg, if ps is the command, in its man pages, it says that ps uses certain files. Also the see also section of the man page tells me to see for sysconf (HP-UX), so now I have got the library which I can use to simulate the ps command Further the See also section of the sysconf has a tressure for me.

However, some one else might certainly have a better approach.

There is no portable way to do this. For HP-UX you would probably use the pstat() stuff. For SunOS, you would probably use the kstat() stuff. I don't know about tru64.

Thanks for your replies ...

That's what I'm looking for .. system calls to get those statistics .. it seems all I can find is shell commands but none of system calls ...

also it seems that /proc directory contains only process statistics .. no server info


I'm desperate ... please kill me

I see two solutions to your problem....

1. Acquire the expertise to reverse engineer the shell commands.

2. Write code to run the shell commands and parse the output.

I like option 1 myself. But I recognize the option 2 may be needed as a stopgap.

'collect' would be a good command to reverse engineer.

Programming documentation can be found at http://h30097.www3.hp.com/docs/pub_p.../PRG_DOCS.HTM.

Are you trying to use gcc or Compaq's C compiler?

Cheers,

Keith

Thanks kduffin for your reply ...
I'm using compaq c compiler (cc) .. and collect seems to generate all the needed information .. however i couldn't find the system calls that it uses ...

I'm not trying to invoke any shell commands like collect inside my program rather to invoke system calls directly because its doesn't have shell commands overhead (the developed program will be deployed on our production servers so effiency is critical)

right now I'm looking at the documentation to see if any would help