Actually it is the same bug, but in your case the second saned process doesn't constantly spam syslog. I've did some more tests and it seems that the syslog-spamming does not always occur on my machine (may be a race condition). As a workaround I wrote a tiny script that kills the second saned process during startup. However, it would be great if the fixed upstream version would be provided as a regular update...
-- saned fails in standalone mode https://bugs.launchpad.net/bugs/671854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
