https://bugzilla.novell.com/show_bug.cgi?id=857372
https://bugzilla.novell.com/show_bug.cgi?id=857372#c50
--- Comment #50 from Johannes Meixner 2014-01-24 15:23:02 CET ---
Regarding
"cups.socket starts cupsd under hood on demand, but who wants it ?"
The only answer I know is: "systemd" wants it.
Of course not the plain systemd software but those who advertise
systemd software features by "just enabling all of them" ;-)
I do not say that those systemd software features are wrong.
But I wonder if enabling them by default is "the right thing".
But I am not an usual user.
I don't know what is "the right thing" for usual users nowadays
so that I cannot decide about systemd's cups/print services
(see my various comments about that problem for me above).
Regarding
"cupsd server says 'forbidden'":
<Location />
Order allow,deny
Allow 127.0.0.2
</Location>
is insufficient, see
http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
the section "Configuring CUPS <= 1.5 in the Network" in particular
"Configuration of the print queues on a CUPS <= 1.5 server" therein
"II) Allow the clients to access the queues."
To configure that use "Share Printers" in the YaST printer module.
FYI:
Regarding enabling/disabling/starting/stopping cupsd
from the YaST printer module, see bnc#769946
In short:
The YaST printer module does not implement own code
for enabling/disabling/starting/stopping cupsd.
Instead the YaST printer module calls YaST functions
that are meant to be used to do that correctly...
;-)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.