help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

problem with hard class, really tricky


From: Christophe Nowicki
Subject: problem with hard class, really tricky
Date: Thu, 18 Aug 2005 11:44:35 +0200
User-agent: Mutt/1.5.9i

Hi cfengine users,

I've started to use cfengine for managing configuration files
of my vservers (http://linux-vserver.org/). I am running many vservers, 
about 30, on my network and cfengine seams to be the best solution for
managing them.

But I can't differentiate with classes one of them.

The name of this host is debian.
This host is running Debian GNU/Linux "sarge".
His FQDN is debian.mynetwork.lan.

I can't use the network interface to distinguish, this host because all
vservers are sharing the same network interface. (/sbin/ifconfig show
all the network interfaces).

When I run cfagent -p -v on the debian vservers, 
I get the fallowing Defined Classes :

192_168_3 192_168_3_10 192_168_3_11 192_168_3_12 192_168_3_20
192_168_3_25 192_168_3_3 192_168_3_30 192_168_3_31 192_168_3_4
192_168_3_5 192_168_3_6 192_168_3_61 192_168_3_7 192_168_3_8
192_168_3_9 32_bit August Day17 Hr22 Hr22_Q3 LoadAvg_low_normal
Min35_40 Min38 Q3 Wednesday Yr2005 any backup_mynetwork_lan cfengine_2
cfengine_2_1 cfengine_2_1_14 compiled_on_linux_gnu dav_mynetwork_lan debian
debian_3 debian_3_1 debian_mynetwork_lan
...
entropy_cfengine_in_low entropy_dns_in_low entropy_dns_out_low
...
ipv4_192_168_3_10 ipv4_192_168_3_11 ipv4_192_168_3_12
ipv4_192_168_3_20 ipv4_192_168_3_24 ipv4_192_168_3_25
ipv4_192_168_3_3 ipv4_192_168_3_30 ipv4_192_168_3_31
ipv4_192_168_3_4 ipv4_192_168_3_5 ipv4_192_168_3_6 ipv4_192_168_3_61
ipv4_192_168_3_7 ipv4_192_168_3_8 ipv4_192_168_3_9 ldap_mynetwork_lan
linux linux_2_6_8_vs linux_i686 linux_i686_2_6_8_vs
linux_i686_2_6_8_vs__1_Wed_Apr_20_04_43_19_CEST_2005 mail_mynetwork_lan



When I run cfagent -p -v on another vserver, I get :

192_168_3 192_168_3_10 192_168_3_11 192_168_3_12 192_168_3_20
192_168_3_25 192_168_3_3 192_168_3_30 192_168_3_31 192_168_3_4
192_168_3_5 192_168_3_6 192_168_3_61 192_168_3_7 192_168_3_8
192_168_3_9 32_bit August Day17 Hr22 Hr22_Q4 Min55 Min55_00 Q4
Wednesday Yr2005 any backup_mynetwork_lan cfengine_2 cfengine_2_1
cfengine_2_1_14 compiled_on_linux_gnu dav_mynetwork_lan debian debian_3
debian_3_1 debian_mynetwork_lan distcc01_csquad_lan entropy_cfengine_in_low
...
entropy
...
ipv4_192 ipv4_192_168 ipv4_192_168_3 ipv4_192_168_3_10
ipv4_192_168_3_11 ipv4_192_168_3_12 ipv4_192_168_3_20
ipv4_192_168_3_24 ipv4_192_168_3_25 ipv4_192_168_3_3
ipv4_192_168_3_30 ipv4_192_168_3_31 ipv4_192_168_3_4
ipv4_192_168_3_5 ipv4_192_168_3_6 ipv4_192_168_3_61 ipv4_192_168_3_7
ipv4_192_168_3_8 ipv4_192_168_3_9 ldap_mynetwork_lan linux linux_2_6_8_vs
linux_i686 linux_i686_2_6_8_vs
linux_i686_2_6_8_vs__1_Wed_Apr_20_04_43_19_CEST_2005 mail_mynetwork_lan


There is no difference between the debian vserver and the other
vservers :

$ diff host.classes.list debian.classes.list 
124d124
< host

The hard class os type "debian" is in conflict with the hostname.
Is it possible to prefix the os type hard classe with something like 
"system_" ?
system_debian, system_debian_3 and system_debian_3_1 etc ?

Or disable the hard classes?

It will avoid the name conflict ;0)

Best Regards,

-- 
Nowicki Christophe                                  
EPITECH Promo 2006                                 
http://people.easter-eggs.org/~cnowicki/

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]