Hi all,
fyi... I've splitted the si_monitor in two sub-commands (maybe someone
of you already know this change).
Now the "si_monitor" is only a daemon that collects clients status and
informations about the installation processes.
The other command I've added is "si_monitortk"; this is a Tk-based GUI
that shows clients status in real-time during the installations.
I think this solution is better than including all the code in a single
command. In this way the si_monitor daemon (maybe I will rename it in
si_monitord) can be optimized to get more information as possibile from
the clients and on the other hand we can add in the si_monitortk
interface more user-oriented features. In this way the monitoring stuff
should be more scalable and also have a better look...
Moreover I'd like to preserve also a console-based (or curses-based)
non-interactive interface to look at the client status. I think this
feature should be very useful for customization, for example to parse
the clients status in a script or something similar... So maybe I will
add another command like si_monitorterminal (or si_monitortext), because
a GUI is very nice, but I love the systemimager command line look.. ;)
Do you agree with this approach? Comments? suggestions?
Regards,
-Andrea
--
Andrea Righi
System Management Group - CINECA - http://www.cineca.it
Via Magnanelli 6/3
40033 Casalecchio di Reno (BO) - Italy
tel: +39 051 61 71 908 (office)
e-mail: [EMAIL PROTECTED]
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
