Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm trying to get memory usage of a process from within that process. I'm calling getrusage, but it always returns zero in ru_idrss. The man page says this field is not even maintained under Linux.
So the question is - which syscall does the VmData line in the /proc/$pid/status come from? Thanks in advance...
/proc is an API. It ain't going to change until a major release comes along - probably not even then. Fields tend to get added, but the fields that exist are (typically) left alone. /proc is not a real filesystem - it's a pseudo f/s that only exists because some kernelspace code decided to expose some (kernel) data. When you read a "file", the data is filled in - at that instant in time, and in response to the act of being read. For your purposes you might be better using /proc/<pid>/statm (or even stat maybe) - note that statm is in pages.
A quick look at (some of) the code indicates that kernel structures are walked to calculate the numbers "on the fly".
procfs FTW!
i have a php-cgi server(website collecting and replying with few processes uptime info) that has system functions disabled, so i cannot extract process uptime/mem usage/etc from a direct shell command, which may even be slower than i do with reading procfs and parsing results. it's just great.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.