Re: [ClusterLabs Developers] Impact of changing Pacemaker daemon names on other projects?

Ken Gaillot writes: > Hi all, > > As I'm sure you've seen, there is a strong sentiment on the users list > to change all the Pacemaker daemon names in Pacemaker 2.0.0, mainly to > make it easier to read the logs. > > This will obviously affect any other scripts and projects

Re: [ClusterLabs Developers] Impact of changing Pacemaker daemon names on other projects?

On 16/04/18 14:32 +0200, Klaus Wenninger wrote: > On 04/16/2018 01:52 PM, Jan Pokorný wrote: >> On 29/03/18 11:13 -0500, Ken Gaillot wrote: >>> 4. Public API symbols: for example, crm_meta_name() -> >>> pcmk_meta_name(). This would be a huge project with huge impact, and >>> will definitely not be

Re: [ClusterLabs Developers] Impact of changing Pacemaker daemon names on other projects?

On 04/16/2018 01:52 PM, Jan Pokorný wrote: > On 29/03/18 11:13 -0500, Ken Gaillot wrote: >> As I'm sure you've seen, there is a strong sentiment on the users list >> to change all the Pacemaker daemon names in Pacemaker 2.0.0, mainly to >> make it easier to read the logs. >> >> This will obviously

Re: [ClusterLabs Developers] Impact of changing Pacemaker daemon names on other projects?

On 29/03/18 11:13 -0500, Ken Gaillot wrote: > As I'm sure you've seen, there is a strong sentiment on the users list > to change all the Pacemaker daemon names in Pacemaker 2.0.0, mainly to > make it easier to read the logs. > > This will obviously affect any other scripts and projects that look