Carlos E. R. wrote:
On 2017-02-04 09:31, Per Jessen wrote:
When your cups doesn't start automatically or you have to keep trying manually, surely there are messages and logs that will tell you what's going on.
That's the problem, nothing to be seen. Nothing in journal, nothing in messages log.
So the main indication is that cupsd isn't running? pidof cupsd? (not seeing any printers could have other reasons). Anything in /var/log/cups/error_log ?
If not, I would try starting cups from the command line, perhaps with strace.
But then it starts.
Okay, so in normal operation there is no problem, it's only during start-up.
The problem is having it started automatically on boot so that when I want to print, it prints. Programs say that there are no printers, that's when I know that it did not start.
Okay.
I would have to hack the service file with strace; but I have the suspicion that systemd doesn't even try to start it.
I meant starting it manually with strace, but you could also try adding it to the service file. You don't need to hack anything, you just override it with a drop-in. I'm not sure how to determine if systemd tries to start it or not - "systemd-analyze critical-chain cups" maybe? # systemd-analyze critical-chain cups.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. cups.service @21.819s └─network.target @21.800s └─wicked.service @1.138s +20.661s └─wickedd-nanny.service @1.124s +12ms └─wickedd.service @1.091s +9ms └─wickedd-dhcp4.service @987ms +90ms └─dbus.service @891ms └─basic.target @855ms └─sockets.target @855ms └─dbus.socket @855ms └─sysinit.target @854ms └─apparmor.service @172ms +681ms └─systemd-journald.socket └─-.slice
I suspect that even though I want cups to start on boot, it doesn't and waits on cups.socket instead.
On my Leap422 client, there is no cups.socket. -- Per Jessen, Zürich (4.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org