Bug 111410 - Cups does not start with "Port 631" in cups.conf after updating to the latest kernel
Cups does not start with "Port 631" in cups.conf after updating to the latest...
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2003-12-03 06:36 EST by jouni
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-12-03 09:30:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Current working cupsd.conf with offending "Port 631" commented out (21.15 KB, text/plain)
2003-12-03 08:31 EST, jouni
no flags Details

  None (edit)
Description jouni 2003-12-03 06:36:19 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 

Description of problem:
After "service restart cups" I get cupsd: Child exited with status 
98! in /var/log/messages and cupsd does not start.

This used to work with same cupsd.conf before updating to kernel-
2.4.22-1.2129.nptl.  Commenting out the line "Port 631" in cupsd.conf 
resolves the problems.

Interesting that this problem started after kernel update

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

How reproducible:

Steps to Reproduce:
1. service restart cups

Actual Results:  cupsd start fails

Expected Results:  cupsd should be running

Additional info:
Comment 1 Tim Waugh 2003-12-03 06:46:50 EST
The redhat-config-printer tool doesn't put 'Port 631' in the
configuration file, so I think you put that there yourself?  In which
case, I hope you removed redhat-config-printer so that it didn't add
Listen lines of its own?

Without seeing /etc/cups/cupsd.conf it's impossible to tell what's up
really.  Could you attach it please?
Comment 2 jouni 2003-12-03 08:31:20 EST
Created attachment 96309 [details]
Current working cupsd.conf with offending "Port 631" commented out

My current working cupsd.cond with offending "Port 631" directive commented out
on line 406.
Comment 3 Tim Waugh 2003-12-03 09:30:52 EST
There is no bug here: you can't say 'Port 631' *and* 'Listen ...:631'.

Note You need to log in before you can comment on or make changes to this bug.