Hide Forgot
Description of problem: Line #138 of /etc/init.d/nfs reads: [ -x /usr/sbin/rpc.idmapd ] && /sbin/service rpcidmapd condstart Should read: [ -x /usr/sbin/rpc.idmapd ] && /sbin/service rpcidmapd condrestart Because condstart is used instead of condrestart rpc.idmapd is always started, even if not running previously Version-Release number of selected component (if applicable): nfs-utils-1.2.3-15 How reproducible: service nfs restart Steps to Reproduce: 1. run service nfs restart 2. 3. Actual results: rpc.idmapd is always started Expected results: If rpc.idmapd is chkconfig'd off it should not start on 'nfs restart' Additional info:
Reproduced on nfs-utils-1.2.3-21.el6: [root@ibm-x3690x5-01 ~]# chkconfig rpcidmapd off [root@ibm-x3690x5-01 ~]# chkconfig --list rpcidmapd rpcidmapd 0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ibm-x3690x5-01 ~]# service rpcidmapd stop Stopping RPC idmapd: [ OK ] [root@ibm-x3690x5-01 ~]# service rpcidmapd status rpc.idmapd is stopped [root@ibm-x3690x5-01 ~]# service nfs restart Shutting down NFS daemon: [ OK ] Shutting down NFS mountd: [ OK ] Shutting down NFS quotas: [ OK ] Shutting down NFS services: [ OK ] Starting NFS services: [ OK ] Starting NFS quotas: [ OK ] Starting NFS mountd: [ OK ] Starting RPC idmapd: [ OK ] Starting NFS daemon: [ OK ] [root@ibm-x3690x5-01 ~]# service rpcidmapd status rpc.idmapd (pid 2052) is running... Verified on nfs-utils-1.2.3-22.el6: [root@sgi-xe320-01 ~]# service rpcidmapd stop Stopping RPC idmapd: [ OK ] [root@sgi-xe320-01 ~]# service rpcidmapd status rpc.idmapd is stopped [root@sgi-xe320-01 ~]# service nfs restart Shutting down NFS daemon: [FAILED] Shutting down NFS mountd: [FAILED] Shutting down NFS quotas: [FAILED] Starting NFS services: [ OK ] Starting NFS quotas: [ OK ] Starting NFS mountd: [ OK ] Starting NFS daemon: [ OK ] [root@sgi-xe320-01 ~]# service rpcidmapd status rpc.idmapd is stopped The line of /etc/init.d/nfs is changed as per comment #0: [ -x /usr/sbin/rpc.idmapd ] && /sbin/service rpcidmapd condrestart
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0964.html