home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!spool.mu.edu!umn.edu!noc.msc.net!news.stolaf.edu!lars.acc-admin.stolaf.edu!johnsonm
- From: johnsonm@lars.acc-admin.stolaf.edu (Michael K. Johnson)
- Subject: YAPPS
- Message-ID: <1992Dec18.063831.24368@news.stolaf.edu>
- Sender: news@news.stolaf.edu
- Organization: St. Olaf College; Northfield, MN USA
- Date: Fri, 18 Dec 1992 06:38:31 GMT
- Lines: 26
-
-
- yes, it is "yet another /proc ps".
-
- I took the classic /dev/kmem ps, the perl /proc ps, and the simple c
- /proc ps posted recently, and made one c /proc ps.
-
- The interface and output is that of the /dev/kmem ps, and the guts are
- those of the simple c /proc ps (but majorly revised). Unfortunately,
- /proc is not quite up to fulfilling the role of /dev/kmem, but if I
- start hacking on the kernel tomorrow, it may come closer ;-)
-
- Right now there are a /lot/ of zeros as placeholders for unimplemented
- stuff... ;-) Try "ps -m", for instance...
-
- I'd like to wait to release it until I know what Linus wants to do (or
- wants me to do) further with /proc, and I have modified to to work
- with that, but if anyone wants to play with it, mail me...
-
- A /dev/kmem proc does have real advantages: for instance, a /dev/proc
- filesystem can't really do the WCHAN field unless some real changes
- are made to the kernel... I just like a ps that doesn't require a
- namelist file, and that doesn't have to be suid or sgid, and is thus
- not a security risk, and doesn't have to be recompiled and updated all
- the time.
-
- michaelkjohnson
-