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. As I may notice 5 days after boot, the journal may have rotated already.
If not, I would try starting cups from the command line, perhaps with strace.
But then it starts. 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. I would have to hack the service file with strace; but I have the suspicion that systemd doesn't even try to start it. If the cups daemon crashed or something there would be evidence in the logs, and there is nothing. I suspect that even though I want cups to start on boot, it doesn't and waits on cups.socket instead.
One problem I have occasionally seen is that services that depend on DNS/network to be available will not be able to start if they're started before DNS is available.
Well... -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)