There really is no ESX rpm though, if its an ESX server, it should be checking for the Vmware kernel. like
"VMware ESX Server 2.1.2 Kernel 2.4.9-vmnix2 on an i686"
as output of uname -a or something of that nature.
-Scott Lackey
cfengine support
On 3/6/06, Jamie McKnight
<[EMAIL PROTECTED]> wrote:
During testing of 2.1.19p1 I noticed that the class VMWare_ESX was defined
on a machine that was not an ESX image or server. Looking at misc.c, it
appears that if you can stat /etc/issue, cfengine defines the VMWare_ESX
class.
src/misc.c:
836 if (stat("/etc/issue",&statbuf) != -1)
837 {
838 Verbose("\nThis appears to be a VMWare ESX system.\n");
839 AddClassToHeap("VMWare_ESX");
840 ESX_version();
841 }
Shouldn't that be checking for the existence of the VMware-esx rpm, or the
existence of the /etc/vmware directory, and not relying on stat'ing
/etc/issue? We drop /etc/motd and /etc/issue files on every host that
print out a big warning banner.
If I need to provide more info please let me know.
Jamie
_______________________________________________
Bug-cfengine mailing list
Bug-cfengine@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cfengine
--
-Scott
_______________________________________________ Bug-cfengine mailing list Bug-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cfengine
