Hello Christoph, after submitting the patch I started thinking about the other architectures as well, but wasn't sure what would be the right way to get this fixed. And yes, taking care of all possible exotic architecture shouldn't be in the responsibility of the upstream software. Especially if other distributions are following a different folder structures like 'lib64' and so on.
In this case I would vote for moving the pacemaker binaries to a more generic directory or even symlink /usr/lib/pacemaker to /usr/lib/<arch>/pacemaker (if that's possible). I also would suggest to remove the i386 arch from the upstream config but keep x86_64 to be in line with lib64 naming stuff, but basically everything folder/location specific stuff should be take care during packaging like you describe before. But as long none of the changes (changing libexec dir or adjusting config.py libdir) the crmsh is basically non-working in the default configuration. As soon as you either patch the config.py, change crm_daemon_dir in crm.conf or change the $PATH variable every change you try to make via crmsh is denied because verify doesn't succeed. To summarize I see multiple options: * change libexecdir to /usr/lib/pacemaker instead of the arch-specific * symlink /usr/lib/pacemaker to /usr/lib/<arch>/pacemaker * configure arch specific crm_daemon_dir in /etc/crm/crm.conf -- Regards Daniel Hoffend
