In particular, tools like the Gnome System Monitor's resource usage graphs are only useful for rough estimates.īottom line: a single (modular) "monitoring daemon" could run continuously and accumulate information in a consistent way. The other problem is data accessibility: each program generates data separately, usually in it's own format, so it is difficult for users to view and even analyze it. However, it only remembers info until shut-down.) (The Gnome Power Manager is a notable exception. In particular, a common problem is that monitoring is done only when requested, not continuously. This means most have no or very limited features for recording the data over long periods of time. Most monitoring programs have been written to allow monitoring the instantaneous value of some parameters. Most of these tools have been written with a single purpose in mind this is a noble thing in principle, but in this case it causes several problems. The venerable program top is an example, as is the Gnome System Monitor or the Gnome Power Manager. Most operating systems have tools that allow viewing some of these properties. Most OS also allow measuring many of their parameters while running (e.g.
temperature, battery charge, processor voltage and frequency). Modern computers have many ways of measuring their run-time properties (e.g. Think of it as extending top and System Monitor with a long-term history feature. It also describes a set of tools and libraries to facilitate displaying this information to the user.
This specification describes the way Ubuntu should gather and record run-time measurements of itself and the machine it's running on. Packages affected: gnome-system-monitor, gnome-power-manager, bootchart, linux (probably)
0 kommentar(er)
