On Mon, Jul 03, 2006 at 11:02:17PM -0700, Bernard Li wrote:
> Let's say the domain name for my cluster is "ocg.org", this is what a node
> entry looks like in dhcpd.conf:
>
> subnet 192.168.0.0 netmask 255.255.255.0 {
> group {
> host oscar01{
> hardware ethernet 00:02:B3:18:AB:BE;
> fixed-address 192.168.0.11;
> filename "pxelinux.0";
> option routers 192.168.0.2;
> option domain-name "ocg.org ocg.org";
> next-server oscar_server;
> }
>
> Notice that "ocg.org" gets repeated in "domain-name".
I haven't looked at the code that generates /etc/dhcpd.conf, but I see
that the top-level definitions in the generated file:
deny unknown-clients;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.150.255;
option domain-name "private";
option routers 192.168.150.101;
ddns-update-style none; # For dhpcd version 3
do the domain-name specification correctly. What is the point of
specifying it again (badly) for each individual host? I see no benefit
in providing the capability for different hosts in the same cluster to
belong to different domains. Why not simply disable the code that puts
an incorrect specification in at the host level?
--
Ted Powell <[EMAIL PROTECTED]> http://psg.com/~ted/
"If you don't look, you don't know."
Dr. Sam Ting, Nobel laureate experimental physicist.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
