On Friday 02 June 2006 19:51, Bernard Li wrote: > Hi Erich: > > > your change will: > > - discard any existing entries and put in only the OSCAR > > interface. Adding an > > entry (and check whether this is necessary at all) would make > > more sense. > > Currently when mkdhcpconf is run (from systeminstaller), dhcpd.conf will > be created from scratch and thus overwrite whatever previous settings > you have. This also applies when you add/delete a node. I could of > course adapt my code accordingly, but we should probably decide the > exact behaviour we want first.
I have added to systeminstaller the possibility to have "appliance" IP addresses managed by DHCP. Actually I thought I could put the appliances in any subnet I want and on any interface (of the master) I want. But I realise this is not the case, they currently must be in the cluster's admin network. So you are right and I was wrong. I'll have to extend this. In that case the appliance definitions might appear in separate "groups" inside the dhcpd.conf file and be served on other interfaces than the OSCAR internal interface. Then the _used_ dhcp interfaces will need to be detected, either by parsing the dhcpd.conf file or by checking all served IP addresses and comparing them with the interfaces' networks. > > - overwrite the /etc/sysconfig/dhcpd.oscarbak file each time > > this is invoked, > > erasing your backup. > > It was never meant to be a "backup", more like a temp file which is > modified then gets moved to /etc/sysconfig/dhcpd. I could of course > create a backup file if necessary. This, of course, is not relevant any more. Thanks for pointing this out! Regards, Erich _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
