Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When a process except cupsd uses the port 631, Samba which enables CUPS can't boot. #1535

Closed
michaelrsweet opened this issue Apr 4, 2006 · 1 comment
Milestone

Comments

@michaelrsweet
Copy link
Collaborator

@michaelrsweet michaelrsweet commented Apr 4, 2006

Version: -feature
CUPS.org User: yasuma

I find a problem about the CUPS function of Samba.

When the cups daemon doesn't work and the port 631 is used by another process, the smbd which enables the CUPS function can't boot.

Even if the port 631 has already used by another process, the smbd connects to the 631 port for the initialisation of CUPS.
And the smbd stalls in the cupsDoRequest().

Because the current implementation of cupsDoRequest() doesn't have any timeout mechanism, it may be difficult to avoid this situation.
I think it needs a enhancement to verify the server daemon or detect the timeout.

I filed this problem to a Bugzilla of Samba.
https://bugzilla.samba.org/show_bug.cgi?id=3604

@michaelrsweet
Copy link
Collaborator Author

@michaelrsweet michaelrsweet commented Apr 22, 2006

CUPS.org User: mike

This will need to be fixed in Samba - CUPS supports non-blocking IO with timeouts...

That said, port 631 is reserved for use with IPP, so any process using that port for something other than IPP is non-compliant...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.