Aravinda VK 80e3832ec1 geo-rep: Fix gluster binary invocation while running as cron ... When scheduler script was executed as cron, it was unable to detect the Gluster binaries. BUG: 1331658 Change-Id: Ic9c533586ed9a472765f69aa2f87d004c46d4340 Signed-off-by: Aravinda VK <avishwan@redhat.com> Reviewed-on: http://review.gluster.org/14111 CentOS-regression: Gluster Build System <jenkins@build.gluster.com> Tested-by: Gluster Build System <jenkins@build.gluster.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> Smoke: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vbellur@redhat.com>		2016-04-29 21:13:59 -07:00
..
generate-gfid-file.sh	extras: geo-rep: Customize the generate gfid script to dirs list	2014-11-26 00:12:18 -08:00
get-gfid.sh	gsyncd: distribute the crawling load	2013-07-26 13:18:57 -07:00
gsync-sync-gfid.c	Core: Fix issues reported by Cppcheck	2014-06-12 04:20:34 -07:00
gsync-upgrade.sh	Regression test portability: mktemp	2014-08-20 13:46:44 -07:00
Makefile.am	geo-rep: Fix gluster binary invocation while running as cron	2016-04-29 21:13:59 -07:00
schedule_georep.py.in	geo-rep: Fix gluster binary invocation while running as cron	2016-04-29 21:13:59 -07:00
slave-upgrade.sh	Regression test portability: mktemp	2014-08-20 13:46:44 -07:00