Bug 97767

Summary: nfs starts before cups --> nfs sometimes binds cups IPP port
Product: [Retired] Red Hat Linux Reporter: dominik schnitzer <dominik>
Component: cupsAssignee: Tim Waugh <twaugh>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: pmitcheson, p.van.egdom
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://www.linuxprinting.org/foomatic2.9/cups-faq.html#q_4_2
Whiteboard:
Fixed In Version: 1.1.19-8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-23 15:46:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description dominik schnitzer 2003-06-20 17:24:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030527
Debian/1.3.1-2

Description of problem:
NFS is started before the cups daemon:
- the nfs components randomly select a free port < 1024 and _sometimes_ select
the cups IPP port.

Which means --> cups cannot start, because the IPP Port is in use and exits with:
--snip--
cupsd: Child exited with status 98!?
--snip--


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. reboot until ;-) lockd for example runs on cups IPP port
2. cups will not start, since tcp/663 is already bound
    

Additional info:

Read: http://www.linuxprinting.org/foomatic2.9/cups-faq.html#q_4_2

Comment 1 Tim Waugh 2003-06-23 15:46:56 UTC
Thanks.  Fixed package is cups-1.1.19-8.

Comment 2 Tim Waugh 2003-06-24 16:28:37 UTC
*** Bug 97958 has been marked as a duplicate of this bug. ***