set use-gss-proxy to true in nfs.conf to be consistent with the
description of 0002-nfs-utils-set-use-gss-proxy-1-to-enable-gss-proxy-by.patch
Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
nfs-idmapd.service would report following error when stopped:
Starting NFSv4 ID-name mapping service...
rpc.idmapd[1198]: Setting log level to 0
Started NFSv4 ID-name mapping service.
rpc.idmapd[1198]: exiting on signal 15
Stopping NFSv4 ID-name mapping service...
nfs-idmapd.service: Main process exited, code=exited, status=1/FAILURE
nfs-idmapd.service: Failed with result 'exit-code'.
Stopped NFSv4 ID-name mapping service.
commit 93e8f092(idmapd: Add graceful exit and resource cleanup)
redirected SIGTERM, so when executing "systemctl stop nfs-idmapd", the
main() of idmapd would running to tail to return, while it returned 1
which considered as error by systemd.
So here just return 0 in main().
(cherry picked from commit 03a9b6b8ca77aa603d265289709eedf032278466)
In commit 104f90f4ce ('gssd: Introduce use-gss-proxy boolean to nfs.conf'),
use-gss-proxy par in [gssd] section of nfs.conf is introduced to
allow the used of the gssprox-mech. However, the default value
of use-gss-proxy is false, which cause different behavor with older
version.
In order to be consistent with the old versions, here we set
use-gss-proxy to true in nfs.conf.
Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
