1. | Which operating systems does KTimemon support? |
|
KTimemon supports Linux® based systems with the /proc file system, Solaris™ based
systems with the kstat library, and Digital
Unix-like (formerly DEC/OSF1) systems with the
table(2) system call interface. Only the Linux®
version has been thoroughly tested, if you experience any problems
with the Solaris™/Digital Unix-like port, please do not hesitate to
contact me.
Also, contributions to KTimemon to adapt it to other platforms are
most welcome. Please contact me at
(m.maierhofer AT tees.ac.uk) if you intend to port KTimemon
to other flavors of Unix-like.
|
2. |
How does autoscaling work?
|
|
Glad you asked. Since there is no sensible predetermined scaling factor
for paging/swapping operations and context switches (unlike for example, memory
utilization, where you can take the total memory size as baseline),
KTimemon uses a semi-intelligent (well, ...) autoscaling
mechanism. Autoscaling works as follows:
Each of the three bar graphs as described in the extended mode section has an associated
scaling factor. The initial values of these factors are set to some
predetermined value.
Each time a new sample is displayed, the respective value is tentatively
scaled with the corresponding factor. If the value can be displayed in
the scale chosen by the factor, no change occurs (that is, small changes in
the activity are reflected by a changing height of the bar).
If the scaled value would be either too large or too small to be
displayed with the current scaling factor, the scaling is adjusted so
that the new value displayed is roughly halfway up the bar graph. Thus,
subsequent changes should have a good chance of getting displayed
relative to the current value, without having to change the scale again.
|
3. |
Why does a message box with diagnostic output from child
command pop up?
|
|
If you bind a mouse button to an external command as described in the
Configuration chapter, KTimemon does
not check for a valid command name. Instead a command shell is invoked
to execute the statement, so shell commands, environment variables and
more can be used. To allow some feedback to the user, KTimemon
monitors the stderr output of the command
shell, and reports it in this message box.
While this scheme can be helpful in case a command is not found, it can
be quite annoying if the invoked command prints harmless diagnostic
information on stderr . A simple and elegant
solution to this problem is to add 2>/dev/null
at the end of the command specification. This redirects diagnostic
messages to message nirvana, and stops the message box popping up.
|
Would you like to comment or contribute an update to this page?
Send feedback to the TDE Development Team