From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218
Description of problem:
When the portmap server is not active (reproduced by "/etc/rc.d/init.d/portmap
stop") starting "redhat-config-nfs" will result in the program crashing - after
it has asked 'nfs service is not active. Do you wish to start it [y/n] (and by
clicking the [yes] button) - when doing a apply of an added 'share'.
I have not succeeded in 100% reproducing this. Sometimes there will be a [nfsd]
server active after doing this. A message can then be seen in the output of
"dmesg" : 'portmap: server localhost not responding, timed out').
Maybe redhat-config-nfs should perform some checkups on the portmap server
before starting (trying to start) the nfs daemon(s).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. /etc/rc.d/init.d/nfs stop
2. /etc/rc.d/init.d/portmap stop
3. (browse to directory for export) --> configure settings --> apply
redhat-config-nfs get confused regarding portmapper status.
Sometime it manages to start a bunch of nfsd processes which in turn don't
(message --> portmap: server localhost not responding, timed out)
Stopping and starting the nfs server with "/etc/rc.d/init.d/nfs stop" doesn't
seem to work then.
maybe it should perform some checks on portmapper availability first.
Red Hat Linux release 8.0.92 (Phoebe)
Should be fixed in redhat-config-nfs-1.0.3-1. QA, please verify.
Fix confirmed with redhat-config-nfs-1.0.3-1.