Bug 161326
Summary: | Bad rewrite of cupsd.conf | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jonathan Kamens <jik> | ||||
Component: | system-config-printer | Assignee: | Tim Waugh <twaugh> | ||||
Status: | CLOSED WONTFIX | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | rawhide | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-06-22 14:15:48 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: | |||||||
Attachments: |
|
Description
Jonathan Kamens
2005-06-22 13:59:01 UTC
Well, what does 'printconf-tui --Xexport' say? And.. did you edit these things by hand in cupsd.conf? Created attachment 115810 [details]
Output of printconf-tui --Xexport
Yes, I edited cupsd.conf by hand. That really needs to be supported, because
as far as I know there's no way to make the changes I made through
system-config-printer.
The reason those changes were made is precisely because there is a way to set them using system-config-printer, and those settings have not been made. Yes, it is certainly bad design for this tool to keeps its own separate configuration and regenerate CUPS configuration from it; however, that is how it *was* designed, so that it what it does. It all needs rewriting so that it *modifies* existing configuration, rather than generating it afresh. See any of the recent fedora-devel discussions about this. If you do need to hand-edit any of the cupsd.conf settings that system-config-printer rewrites, you *must* remove system-config-printer or they will get overwritten. You write, "The reason those changes were made is precisely because there is a way to set them using system-config-printer, and those settings have not been made." I've searched and searched and can find no way in system-config-printer to set ALLOW FROM for a printer or to add a LISTEN to cupsd.conf. If, indeed, there is a way to set them as you say, can you give me a hint about where I might find it in the UI? /usr/share/doc/system-config-printer-0.6.*/printconf-share.html Nope, sorry, Action > Sharing... in system-config-printer won't allow me to set *either* of the settings I'm trying to set that are shown in the diff above. I want to do "Allow From @LOCAL", and the UI does not, as far as I can tell, allow "@LOCAL" to be entered. And as far as I can tell there's no where in the Sharing... dialog that allows me to specify what IP addresses the CUPS Web server should listen on. As for @LOCAL: you can tell it to listen on specific interfaces if you like -- at any one time, this is equivalent to @LOCAL. As for particular IP addresses to *listen on* -- well, it will listen on the local IP address for each interface you want it to listen on. Is that not sufficient for what you want? Regarding @LOCAL: I shouldn't have to specify each network interface explicitly in system-config-printer when CUPS supports the very useful @LOCAL functionality. I should be able to specify @LOCAL or the equivalent to system- config-printer and have it put @LOCAL in cupsd.conf as a result. Yes, I can list all my local network ranges explicitly for each printer, but that's a workaround, not a fix -- the fix would be for system-config-printer to know how to do @LOCAL. Concerning listening, I think you're confusing the IPP protocol listening with the admin Web server listening. I'm talking about the latter, not the former. There is no way in system-config-printer to specify which IP addresses the admin Web server should listen on. When system-config-printer creates cupsd.conf, it always inserts just "Listen 127.0.0.1:631". |