Re: interpreting gkrellmd output
"John Sanabria" <[email protected]>
| Newsgroups | gmane.comp.gnome.apps.gkrellm |
|---|---|
| Message-ID | <[email protected]> |
Thanks a lot, so useful information. The other hand, there exist a project to record the data collected from gkrellm daemon and store it for example in a rrd database. thank you again, regards. > On Thu, 29 Mar 2007 23:01:34 -0400 (AST) > "John Sanabria" <[email protected]> wrote: > >> This information was get from virtual node. I wanna know where i can >> found >> documentation about what is the meaning of all that numbers. for >> example: > > There's not a real doc on this, so I'll just note here what the numbers > are. > Times and bytes for chart monitors transmitted at each update are > cumulative totals over time. > >> <cpu> >> 0 33322 33 12962 2223770 > cpu-number user-time nice-time sys-time idle-time > >> <proc> >> 100 1 18422 0.00 0 > n_processes n_running n_forks load n_users) > >> <net> >> eth0 307818998 10378546 >> lo 9027288 9027288 >> sit0 0 0 > interface-name receive-bytes transmit-bytes > >> <inet> >> +0 39c 136.145.116.114:801 > +0 is a connection flag which means this line is a new active IPv4 > connection. > +6 would be IPv6 and -0 or -6 means line is for a closed connection, so: > connection-flag local-port remote-address:remote-port > >> <mem> >> 268619776 139804672 3411968 0 21344256 104058880 > total-memory used free buffers cached > >> <swap> >> 567533568 36864 0 9 > swap-total swap-used swap-pages-in swap-pages-out > >> <time> >> 35 42 22 29 2 107 4 87 0 > Values from struct tm > tm_sec tm_min tm_hour tm_mday tm_mon tm_year tm_wday tm_yday tm_isdst > > And others: > > <disk> > {disk-partition} disk-name read-blocks write-blocks > > <routed> > net-interface-name routed-event > > <fs> > mounted-directory device blocks blocks-available blocks-free block-size > > <fs_fstab> > mounted-directory device type > > <fs_mounts> > mounted-directory device type blocks b-avail b-free b-size > > <mail> > mail-path total-mail new-mail > > <battery> > present on-line charging percent time-left battery-id > > <sensors> > type name id iodev interface value > > <uptime> > minutes > > <timer> > name minutes > > > Ask if you need additional explanation on any particular part. > > Bill > _______________________________________________ > Gkrellm mailing list > [email protected] > http://lists.jutley.org/cgi-bin/mailman/listinfo/gkrellm > http://ece.uprm.edu/~s047267 http://del.icio.us/josanabr http://blog-grid.blogspot.com _______________________________________________ Gkrellm mailing list [email protected] http://lists.jutley.org/cgi-bin/mailman/listinfo/gkrellm