Wasn't there a bproc kernel module ? The ideal thing would be to access all
nodes' /proc on one machine.
> I've also written a little daemon that I call procd. It is a simple
> socket based app that listens for a connection on a specified TCP port.
> You telnet to the port and type the name of the file you want to view. It
> restricts the files you can see to those available from /proc. So if you
> want /proc/cpuinfo that's exactly what you type into your telnet session
> and you get the results right there. There isn't any reason why another
> program couldn't be written to communicate with this one. The output from
> the file requested continues until you see a '.' on a line by itself, much
> like the termination of a DATA segment in SMTP, so it would be easy to
> parse.
> This runs as a nonpriveleged user also, no need for root.
> I don't have this up on the web yet so if anyone would like to see it
> just drop me an email. Its GPL'd, as it should be.
> -M@
This almost exactly describes what I'm doing, except that I plan to add
some authentication and a couple of other commands, and that I do the
actual querying with a perl script rather than telnet. perl parses
anything totally trivially.
Great minds think alike, eh? :-) I'd love to see your source just to see
if I left anything out of mine -- being lazy, I actually send a "done"
to the caller instead of a "." (in perl, just /^done/ which is actually
a bit more readable than /^\./:-) and haven't actually installed the
"send filename" command, but it is next on the agenda, possibly this
very afternoon.
Thanks,
rgb
