On Mer, 2005-02-02 at 15:31, Tom Shilson wrote: > I wanted to follow control blocks in Linux memory from 'outside' of Linux > by using VM commands. It worked on lots of other programs and operating > systems. The problem is that the documentation just isn't there. We're not > in the mainframe world any more. I don't have much experience reading C, so > I gave up, at least for now.
I'm not really up on peeking into images from the outside but there are certainly problems trying to pull information. The OS itself uses dynamically allocated memory for almost all system objects (uptime and a few other exceptions exist). They are also dynamically allocated/freed and reused for other things so you need locking. You can probably safely pull a few symbols like the load average, if the linux is idle and much of the time the name (to 14 chars) of the process running. Not much else. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
