Portmap against cups

Boris Vinarsky borisv at rambus.com
Tue May 27 12:07:03 PDT 2008

We noticed that occasionally CUPS service fails to start on our RHEL4 desktops because port 631 was busy. The reason was that portmapper service which selects ports in the range 600-1023 essentially randomly would assign ports 631 to ypbind or nfs.lock which start before cups.

This issue is discussed at https://bugzilla.redhat.com/show_bug.cgi?id=103401

Does anybody have a good idea on how to resolve this collision?

Thank you,


More information about the cups mailing list