Carlos E. R. wrote:
On 2017-01-30 23:09, John Andersen wrote:
On 01/30/2017 10:46 AM, Carlos E. R. wrote:
Now, what must I do so that cups does start on boot? Or a minute later, doesn't matter. I have to start it manually, some times several times till it holds.
Cups.service needs these to start:
requires: sysinit.target(active), system.slice(active) conflicts: shutdown.target(dead) wanted by: multi-user.target(active) after: basic.target(active), network.target(active), sysinit.target(active), system.slice(active), systemd-journald.socket(running) before: multi-user.target(active), shutdown.target(dead)
Note this is the inheritied requirements as well as the direct requirements. The cups.service is actually quite simple:
[Unit] Description=CUPS Printing Service After=network.target
[Service] ExecStart=/usr/sbin/cupsd -f
[Install] WantedBy=multi-user.target
One of the conditions (or inherited conditions) listed above is not coming true, or shutdown.target is not going away. Are you shutting down, or are you suspending? Is your network slow to start?
The problem arises after a full reboot. If I activate the service manually, then hibernate, cups stays alive, I think.
As you would expect, right?
Network is not using dhcp on this machine.
systemd-analyze blame: 20.590s wicked.service
That seems pretty normal. 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. If not, I would try starting cups from the command line, perhaps with strace. 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. -- Per Jessen, Zürich (3.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org