|
Bugzilla – Full Text Bug Listing |
| Summary: | Can't configure CUPS to listen to remote IPP packets | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Dennis Conrad <dcon> |
| Component: | Printing | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Johannes Meixner <jsmeix> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jsmeix |
| Version: | RC 2 | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Beta-NTS | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | YaST2 Log Files | ||
|
Description
Dennis Conrad
2005-09-13 12:10:10 UTC
Created attachment 49759 [details]
YaST2 Log Files
Same on my RC1 system. Seems the message can be simply ignored. Dennis, does it work as expected if you simply click [OK] at this message? I.e. is the cupsd "insserved" and started on your system? To verify do: insserv -r cupsrenice insserv -r cups rccups stop And then do the same again and click [OK] at the message. Is then cupsd "insserved" and started on your system? Michal; note that there is a new additional service "cupsrenice" which was introduced for faster booting. Therefore: 1. Only "insserv -r cups" would fail with: insserv: Service cupsd has to be enabled for service cupsrenice 2. Only "insserv cups" may not result the default behaviour (cupsrenice may be missing). 3. Same problem for "rccups stop/start" versus "rccupsrenice stop/start" (what must happen first, what next)? I don't know the exact dependencies and details about cupsrenice, plase ask Klaus Singvogel for details. It actives cups, but it doesn't activate cupsrenice. However, as no configuration is written, printing simply doesn't work - that's the biggest problem :-) Dennis, What else except - activating of cupsd (i.e insserv) - starting of cupsd (i.e. rccups start) do you expect from "CUPS to listen to remote IPP packets"? Of course in cupsd.conf there must be appropriate settings for Browsing but this settings are there by default: Browsing On BrowseAllow @LOCAL Was at Dennis' system. YaST did set up everything so that it works. In particular it activates cupsd and set in cupsd.conf "Browsing On". Dennis' system didn't get Browsing information from our CUPS server because the DHCP netmask for Dennis' system was such that his system was not in the same network as our CUPS server (i.e. "BrowseAllow @LOCAL" rejected all Browsing information from our CUPS server). After fixing Dennis' netmask it worked. It seems YaST didn't activate cupsrenice but this desn't cause a big problem because: cupsd is started by default with "ionice -c 3" cupsrenice does "sleep 40" and then "ionice -c 1" for the cupsd processes If YaST didn't activate cupsrenice, cupsd will stay in "ionice -c 3" i.e. cupsd will stay in slowest IO mode but nevertheless it should work. Reduced severity to normal. I remove that warning (still in log) Michal, I talked to Klaus Singvogel regarding "cupsrenice". There is no need that YaST cares about "cupsrenice". I.e. ignore all what I wrote above about "cupsrenice". Only "rccups start/stop" is perfectly sufficient. To verify, see /etc/init.d/cups: "ionice -c 3" is only called if the system boots into runlevel 5. I know, I should have read /etc/init.d/cups myself more carefully before causing confusion with "cupsrenice". |