FAQ
Q1. Is it required when process controllers exist for GNOME(System Monitor) and KDE(kpm) are available ?Q2. Do i have to compile anything ?
Q3. What are the requirements ?
Q4. From where do I get these ?
Q5. Do I have to make any adjustments after installing the above dependencies ?
Q6. Script is unzipped.What next ?
Q7. What are the other possible configurations ?
Q1. Is it required
when process controllers exist for GNOME(System Monitor) and KDE(kpm) are
available ?
Ans. The main aim of this script is to ease the
GUI user to give him a comfortable integrated utility and not to give the
linux users another powerful process controllers like the above two. The
above utilities may be much more powerful than this script but they don't
integrate HALT, REBOOT, SUSPEND MONITOR and LOCK buttons. With these
buttons you can just press the hot key you assign to do anything you want.
Also note that since it is an interpreted script you can change any part of it at anytime and it does not need to be recompiled.
Q2. Do i have to compile anything
?
Ans. No. It is an interpreted script. You just
have to unzip it (if it is zipped)
Q3. What are the
requirements ?
Ans . For the Tk version you need Tcl/tk
. For the gnocl you need gnocl. Also Independent of these (Tk/gnocl) you
need xscreensaver and xset .
Q4. From where do I get these
?
Ans. Most of these are by default installed
on a typical RedHat system. The only one which you might not have is gnocl.
For those who want to get and know more about gnocl the link to the site
available to me when writing this page is
http://www.dr-baum.net/gnocl/
Q5. Do I have to make any adjustments
after installing the above dependencies ?
Ans. Only for the gnocl version . Since the gnocl
distribution does not have any "make install " option i have copied
the "gnocl.so" file to "/usr/lib/gnocl.so" . You will have
to do the same thing for it to work.
Alternately you can edit the script to change
the line where the file "gnocl.so" is loaded to the path where you gnocl.so
is located.
Q6. Script is unzipped.What next
?
Ans. After unzipping it to some location please
verify that it has execution rights. If it does not have then you can type
#> chmod +x acd.tk ( or the corresponding
file )
at the shell prompt.
Next you bind it to a Hot Key (preferably alt+ctrl+del combination ) . This is done in various different ways for different window managers. Control Center in KDE and GNOME. WPrefs in Windowmaker . You may refer to the window manager specific documentation for bindnig an application to a key. The normal procedure is first select the key combination and then write the completed path of this script along with it's name you have saved it as.
Now press the hotkey and enjoy.
Q7. What are the other possible
configurations ?
Ans. You can do many changes with the scripts
(at your own risk). The important changes that can be made are
- Changing the color of the application
- changing the "kill" to "kill-9" in the kl function as this helps to kill the programs which do not respond to normal kill command
- you can comment or uncomment a few lines to toggle between modal and non modal feature ( read Known Bugs)
Known Bugs
The most important bug is that if you continuously keep the hot key pressed then many occurrences get initiated many time and if you have enabled the script to become modal then you may have only one option left Alt+Ctrl+backspace or reboot. The other bug is that it shows itself in the process .this might not be considered as a bug and can be modified by changing a few lines in the function which gets process list.Note that this bug has been successfully removed from the gnocl version.
In the gnocl version due to the bug in gnocl itself when you kill the application it may cause memory leak.
Future Feature
Removing bugs is the foremost consideration
Providing a refresh button
providing other signals that can be sent to the
selected programs.... are some of the future development considerations