Red Hat Bugzilla – Bug 216440
rpc.statd ate my CUPS
Last modified: 2007-11-30 17:11:49 EST
Description of problem:
When a system has both NFS and CUPS, the nfslock service starts first during
boot and always gets assigned port 631, which causes CUPS startup to fail.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enable CUPS
2. Enable nfslock
CUPS fails to start as port 631 already in use
CUPS should start
Could fix this by setting the port used by rpc.statd to a safe value with
the -p option, or by moving CUPS before portmap in the boot sequence.
According to the manual page, rpc.statd requests a port from the portmapper. I
don't see a way to tell the portmapper what range is acceptable though., so
possibly this is a bug report/feature request for the portmapper.
Yes, I can confirm this. This conflict beat my coworker computer twice at this week.
You can explicitly set the port statd
will listen on by setting the STATD_PORT
variable in /var/sysconfig/nfs which
should help avoid this problem
That should work. This should be set by default though. It doesn't appear to
be on by default in my FC6 setup.
in more recent nfs-utils I've added a fully populated
/etc/sysconfig/nfs file that should help...
is this backported for fc6 too?