Bugzilla – Bug 142078
portmap not $portmap in /etc/init.d/* dependencies
Last modified: 2006-01-09 17:05:49 UTC
I installed a workstation this weeked with my boxed copy of SUSE 10. Eventually I used yast to add some nfs mounts and rebooted. The boot process hung while mounting the NFS mounts. Eventually I realized it was because portmap was not being started. I tracked it down to using $portmap not 'portmap' in the init scripts. I changed $portmap to just portmap and rebooted and everything worked.
Sorry but this can not work. The system provide `$portmap' is mapped in the configuration file /etc/insserv.conf to `portmap'. Therefore this works as it should, at least for all machines around here. Please check your /etc/insserv.conf, there should be a line # # SunRPC portmapper available # $portmap portmap which leads the program insserv to map `$portmap' to 'portmap'. See manual page of insserv with `man insserv'.
Hmm, that's strange. It was definately not getting started, and that was the only change I made. I'll note that nfsserver does /not/ use $portmap but rather 'portmap': (All greps taken from *unmodified* init files, verified with rpm -V) nfsserver:# Required-Start: $network $remote_fs $named portmap nfsserver:# Required-Stop: $network portmap Also: svcgssd:# Required-Start: $network $remote_fs $named portmap svcgssd:# Required-Stop: $network portmap xinetd:# X-UnitedLinux-Should-Start: portmap autofs cups:# Should-Start: earlykdm hotplug named portmap ptal slpd printbill hplip cups:# Should-Stop: portmap gssd:# Required-Start: $network $remote_fs $named portmap gssd:# Required-Stop: $network portmap idmapd:# Required-Start: $network $remote_fs $named portmap idmapd:# Required-Stop: $network portmap I'll have to check the other machine to see if I can reproduce the behavior after I change the init scripts back and re-run insserv -d. Weird.