Hi everybody, Sorry this got a little long - if you don't use lrpStat or don't care much for it, you can skip this message. With the help of my company, I'm currently working on designing a complete rewrite of the LrpStat tool. The main focus will be making it more versatile, i.e. enabling it to monitor pretty much anything one can think of. The server side will consist of a program written in C that communicates with the clients, using plugins to actually gather the data. Using shell-scripting will no longer be supported, since I just don't see the benefit of spawning off several processes just to gather some information (and doing so every second or so). Leaf/LRP will still be the main target plattform, so low impact on the server (in memory as well as CPU-usage) is still a must. The client side will be a Java applet/application (as before) but since we want it to be much more flexible, we'll go for a re-implementation rather than just adding one "cludge" after another (besides, I want to implement all mulit-threading issues I learned about while writing the original version and I want to make it more "object oriented" than the current design is (on the code level - there's far too much of copy&paste in the current version for my taste)). Ontop of that, we're thinking about generic clients for Windows (probably using VB - that's what I do to make a living) and Linux (using C/C++). The linux client will probably be a Gnome applet, since that's what's used at my office. Of course, all of this will still be under a GPL license, even for the code that's written on my company's time. The information that's gathered will include: network information (obviously), CPU info (CPU-usage, processor load), environmental info (temperature, fan speed and so on, heavily relying on lmsensors), number of logged in users, number or running processes and so on. I would like to add some monitoring of our UPS as well, but since that's connected to our NT-Server, I'm not quite sure that will happen. What I'd like to know is if any of you have any features you'd like to see implemented. That is, certain info to be monitored in real time as well as any "crazy" way (meaning, a way I haven't thought of yet - the ways I thought of so far can be seen from having a look at lrpStat as it is right now) to represent the data on the client side. And of course, anything else you might have thought about "wouldn't it be nice if we could..." (well, as long as it's connected to monitoring something on your server/router - lrpStat will never do laundry, sorry ;-)). I _am_ considering working on a NT server component, but that's surely not as easy as I thought it would be (writing a service is the least of my problems, actually getting one's hands on any interesting data is much more so). Anyway, if anybody of you has a request you'd like to see implemented in a future version of lrpStat, now's the time, since we're still in the design phase, not having written a single line of code yet (well, aside from the fact of finding out how those "plugins" on the server side component might work). I won't promise that every suggestion will be implemented, but I will surely give it some serious thought. The "home" of this new project will still be my homepage (http://lrp.hejl.de) as well as the leaf mirror (http://leaf.sourceforge.net/devel/hejl/) The original version of lrpStat is close to reaching its "stable" status, so unless any issues arise during the next couple of weeks, version 1.0 (non beta) will be released before any coding work will be done on the recode (without any new features, just bug fixes, if bugs should arise). Thanks for any suggestions. Martin _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-devel
