I am attaching an strace log. For this I restart avahi-daemon to assure that it is not on 100% CPU. CUPS is running. Then I run
sudo strace -ftvvs 65535 -p PID 2>&1 | tee log with PID being the process ID of avahi-daemon. I have restarted CUPS at 23:58:50, then I have restarted CUPS at 23:59:31 and the restart command took until 23:59:38. I stopped CUPS at 00:01:24 and it took until 00:01:26. The log ends at 00:03:25. Note that avahi-daemon did not spin up this time. It seems only to spin up if it is not coupled with strace. strace seems to slow down avahi- daemon and this way avahi-daemon does not go wild when CUPS is registering its print queues. After decoupling strace and starting cups again not under observation by strace, avahi-daemon spins up. So we should run avahi-daemon under strace by default, simply piping the log to /dev/null ... For me it seems a timing problem. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1059286/+attachment/3384076/+files/log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059286 Title: avahi-daemon takes 100% CPU right after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1059286/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
