On 03/03/2016 at 08:01 PM, Minfei Huang wrote:
On 03/03/16 at 07:40pm, Xunlei Pang wrote:
> For large number of machines, they should rely on dhcp to deploy,
> specifying DNS directly through /etc/resolv.conf is not standard,
> the info will be overridden by the info in ifcfg files and dhcp after
> each reboot (I verified this both on RHEL and fedora), so it would
> be better if kdump can follow the same way as RHEL and fedora.
It can be fixed, if there is local script to appending specific DNS
after /etc/resolv.conf being generated by NM.
Then in dhcp cases we can't decide whether one entry in
/etc/resolv.conf is generated by dhcp or user local scripts.
It will make some trouble if dealing with /etc/resolv.conf
especially in the dhcp cases.
Also what if the local script appends DNS to /etc/resolv.conf
dynamically: one day generate 1.1.1.1, another day generate
2.2.2.2 instead of 1.1.1.1, so it's hard to support all those
non-standard and peculiar cases.
Regards,
Xunlei
> If customers want to add extra DNS to kdump, the recommended way
> is specifying them in the corresponding ifcfg file. But they also can do
> it through cmdline using dracut's "nameserver=" command, or just
> specify them in /etc/sysconfig/kdump via KDUMP_COMMANDLINE_APPEND.
>
> Just regard /etc/resolv.conf as a temporary volatile memory.
The net device name may be different with other machines. It's hard to
configurate DNS in ifcfg-$dev using script.
Thanks
Minfei