From 50ca15e14e287f366576f257d715318d2514d7fa Mon Sep 17 00:00:00 2001 From: He Min Date: Thu, 2 Jan 2020 14:26:22 +0800 Subject: mgmt/glusterd: Correct the log path of valgrind. Problem: Currently enabling run-with-valgrind will cause the gnfs and quota to fail to start. The phenomenon is as follows. ------------------------------------------------------------------------------ NFS Server on localhost 2049 0 N 48406 Quota Daemon on localhost N/A N/A N 48428 ------------------------------------------------------------------------------ Solution: The cause of the above phenomenon is that the log path of valgrind is set incorrectly. Gnfs and quota can start with valgrind normally after correcting the log path. Updates: #788 Change-Id: Ib91408c08522ff66afff908fbff3fce4b93ea770 Signed-off-by: He Min --- xlators/mgmt/glusterd/src/glusterd-svc-mgmt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'xlators/mgmt') diff --git a/xlators/mgmt/glusterd/src/glusterd-svc-mgmt.c b/xlators/mgmt/glusterd/src/glusterd-svc-mgmt.c index f4f39d9ca27..99119d69e45 100644 --- a/xlators/mgmt/glusterd/src/glusterd-svc-mgmt.c +++ b/xlators/mgmt/glusterd/src/glusterd-svc-mgmt.c @@ -189,7 +189,7 @@ glusterd_svc_start(glusterd_svc_t *svc, int flags, dict_t *cmdline) if (this->ctx->cmd_args.valgrind) { len = snprintf(valgrind_logfile, PATH_MAX, "%s/valgrind-%s.log", - svc->proc.logfile, svc->name); + svc->proc.logdir, svc->name); if ((len < 0) || (len >= PATH_MAX)) { ret = -1; goto unlock; -- cgit