https://bugzilla.novell.com/show_bug.cgi?id=857372
https://bugzilla.novell.com/show_bug.cgi?id=857372#c49
--- Comment #49 from Daniel Pecka 2014-01-24 14:02:17 UTC ---
@Johannes
i confirm what you say .. when you just disable cups.socket and let do
cups.service its job done it works as expected ..
just using common sense, cups.socket starts cupsd under hood on demand, but who
wants it ?.. current state with yast not supporting cups.socket and requirement
for user being cups.socket-aware is sick ..
i go finally to make things clear (i suppose that we want it listening on
0.0.0.0):
1) create /etc/systemd/system/cups.socket with content:
[Unit]
Description=CUPS Printing Service Sockets
[Socket]
ListenStream=/var/run/cups/cups.sock
ListenStream=0.0.0.0:631
ListenStream=[:::1]:631
ListenDatagram=0.0.0.0:631
ListenDatagram=[:::]:631
BindIPv6Only=ipv6-only
[Install]
WantedBy=sockets.target
2) systemctl reenable cups.socket .. this will create symlink to this file
instead of default symlink target /usr/lib/systemd/system/cups.socket
3) edit by hand (or yast cups) /etc/cups/cups.conf and change Listen var to:
Listen 0.0.0.0:631
4) systemctl restart cups.service
after these steps is cupsd accessible from the network as expected and started
on demand by socket
Problems:
a) yast doesn't support it so it assumes user will do it by hand
b) i don't know why, cupsd server says "forbidden" (but i can access it) ..
perhaps something wrong with this section (etc/cups/cupsd.conf)?
# Web interface setting...
WebInterface Yes
# Restrict access to the server...
<Location />
Order allow,deny
Allow 127.0.0.2
</Location>
# Restrict access to the admin pages...
Order allow,deny
</Location>
--
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.