On 03/28/2014 06:11 PM, Vivek Goyal wrote:
> So in following patches, I will introduce new options in
kdump.conf. With those
> patches kdump will not use /etc/fence_kdump_nodes file (this will be replaced
> with fence_kdump_nodes option in kdump.conf). But not to break Pacemaker API
> during Pacemaker fence_kdump configuration content of /etc/sysconfig/fence_kdump
> will be read and store into fence_kdump_args in kdump.conf in initial ramdisk.
Marek, are you particular about maintaining this file. No package owns
this file so asking user to create this file and provide options here
Do you mind if we change it and ask user to specify options in
/etc/kdump.conf using fence_kdump_args options.
Fence agents do not use
configuration files at all and they are not
dependent on pacemaker or any other cluster software. So this change
will not have any impact on them. imho the pacemaker team is the one who
should answer your questions.