You are not logged in.

#1 2014-09-20 16:36:20

pjezek
Member
From: Praha - CZ
Registered: 2005-05-19
Posts: 79

journalctl with no PID message for cups and avahi contemporary failure

I have facing a persistent problem with avahi-daemon and cups as systemd services. They have been enabled but fallen in a failed state as being started. Any investigation of the failures by journalctl (using _PID=) returned no useful info (log period only). Is there another way how to find why the services failed? A dependency between cups and avahi should be IMHO optional and recommended only for those using printers connected remotedly (or managable by users in cups.conf).  I cannot identify wheather the failures are caused by systemd issue, some wrong config file or missing some needed file. Any idea? Thank you all.


Our tomcat for your mice! Archlinux for your comps! Alfa Romeo for your roads! Faster running guaranted!

Offline

Board footer

Powered by FluxBB