-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2007-05-08 02:20:03 UTC by sf-robot
-
News Header
Linux Cluster Manager Solaris Client 2.75 has been released. LCM is a graphical tool for monitoring and managing multiple Linux and now Solaris systems from a central location. Features include real time monitoring and status information, remote command execution, and a range of imaging features.
Feature Enhancements
- LCM is now capable of monitoring Solaris 10 clients as well...
2007-04-23 02:38:58 UTC by mjengland
-
Linux Cluster Manager 2.75 released. LCM is a graphical tool for monitoring and managing multiple Linux systems from a central location. Features include real time monitoring and status information, remote command execution, and a range of imaging features.
Feature Enhancements / Bug Fixes
- Debian port is complete fixing a long list of bugs for that platform
- Source distributions have...
2007-04-14 17:50:46 UTC by mjengland
-
Dependencies have been corrected in the upcoming LCM release.
2007-04-14 00:38:05 UTC by mjengland
-
Peter, thanks for your comments. Some things that I am working on:
1) Solaris 10 client port is almost done. It is functional from a monitoring perspective but not quite clean yet, still some optimizing that can be done
2) Historical data. I do have a prototype written to capture historical performance data to a CSV file. My idea is to provide this functionality in a future release and...
2007-02-06 16:41:26 UTC by mjengland
-
Very nice product. Looking good...
For better or worse, here are a few feature requests..
ipmi support (for systems with iLo's). Allows system restart/shutdown etc when node has hung hard (OpenIPMI 2.0.7 i think is current stable).
plugin support for ganglia ? or use rrdtool or similar directly for maintaining monitor data output (useful for following historical errors).
Monitoring...
2007-02-05 10:19:21 UTC by nobody
-
I thought I would include an example for those that are curious. The numbers below are not accurate and only meant for illustration:
Original System:
/ - 1GB (block 1 - 2048)
/data - 512MB (block 2049 - 3073)
/data2 - 512MB (block 3074 - 3098)
/home - 1GB (block 4099 - 6147)
If /data is excluded the deployed client will look as follows:
/ - 1GB (block 1 - 2048)
/data2 - 512MB...
2006-12-17 22:54:58 UTC by mjengland
-
This can be accomplished through standard Unix commands although I will consider it for a future release, no promises.
For now here a Unix command that will do the job:
kill $(ps -ef | grep | tr -s " " | cut -d " " -f2)
Michael.
2006-12-17 22:49:23 UTC by mjengland
-
The exclude option will produce a directory that is empty when the image is deployed. This is because the directory belongs to the top level partition but the contents belong to the excluded one.
Yes, you can have multiple exclude entries in /etc/lcm.conf as follows:
exclude =
for example:
exclude = /data /data1 /test
Remember these are not NFS mounts as...
2006-12-17 22:39:17 UTC by mjengland
-
You can use the tool to do this today and standard Unix shell commands. If you want to kill a job with a specific name execute:
kill $(ps -ef | grep | tr -s " " | cut -d " " -f2)
You can target this at specific nodes or let it run across the entire grid. Let me know if this works for you or if you have other ideas on how you would like to see something implemented...
2006-12-06 17:29:32 UTC by mjengland
