Description of problem: backport from master Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Change-Id: I6523894416cc06236ea1f99529efd36e957bd98e
https://review.gluster.org/c/glusterfs/+/21246
REVIEW: https://review.gluster.org/21246 (georep: fix hard-coded paths in gsyncd.conf.in) posted (#2) for review on release-4.1 by Kaleb KEITHLEY
COMMIT: https://review.gluster.org/21246 committed in release-4.1 by "Kaleb KEITHLEY" <kkeithle> with a commit message- georep: fix hard-coded paths in gsyncd.conf.in This is part of the reason why we use autoconf (i.e. configure). For an ordinary clone+autogen.sh+configure SBIN_DIR is /usr/local/sbin; for an rpm or dpkg build it will be /usr/sbin. I wonder how many more are lurking in our sources? /usr/libexec is one that frequently bites us on Debian and Ubuntu, which don't have /usr/libexec. (But it's all Linux, right?) See https://bugzilla.redhat.com/show_bug.cgi?id=1601532 Reported-by: lohmaier+rhbz Change-Id: I6523894416cc06236ea1f99529efd36e957bd98e updates: bz#1632013 Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-4.1.6, please open a new bug report. glusterfs-4.1.6 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2018-November/000116.html [2] https://www.gluster.org/pipermail/gluster-users/