I (finally) upgraded our main server from 13.1 to 13.2. Overall it went quite smoothly.
What did not work was that CUPS startup has changed in some way that did not get upgraded along with the rest of the system. In 13.1 I could start CUPS with “/etc/init.d/cups start”. That is no longer possible in 13.2; the file </etc/init.d/cups> has disappeared.
So I suppose it must be started by systemd as a service. Okay. When I look at Yast::System::Services Manager, there is no cups option. Also, there is no way to add a service from the manager.
> What did not work was that CUPS startup has changed in some way that did
> not get upgraded along with the rest of the system. In 13.1 I could
> start CUPS with “/etc/init.d/cups start”. That is no longer possible in
> 13.2; the file </etc/init.d/cups> has disappeared.
You should use “systemctl start cups.service” to start it, same as you
should do in 13.1 as well. And use “enable” so that it starts
automatically next time.
Well, yes, I could do that (and did); it would handle this particular instance. That does not really answer my question, though.
More generally, How does one find and add a new service to 13.2?
CUPS was missing after the initial upgrade. After installing the 1100 updates, CUPS appeared in the Service Manager.
Annoyingly, named (address resolver) refuses to start at boot time. I have enabled and activated it in the Service Manager; no joy. As a workaround I added it to root’s crontab with @reboot.
On 2015-05-04 07:06, jimoe666 wrote:
> CUPS was missing after the initial upgrade. After installing the 1100
> updates, CUPS appeared in the Service Manager.
You mean that the CUPS rpm package was not installed? Strange.
Maybe there was a bug that was solved with an update, and you needed to
apply it — so after you installed the updates, it worked.
> Annoyingly, named (address resolver) refuses to start at boot time. I
> have enabled and activated it in the Service Manager; no joy. As a
> workaround I added it to root’s crontab with @reboot.
Well, what you have to do is investigate in the logs why it fails to
start. Maybe network is not up early enough.