Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#22573 - [sane] saned spams syslog
Attached to Project:
Arch Linux
Opened by José Pedroso (josedpedroso) - Sunday, 23 January 2011, 21:32 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 26 January 2011, 14:07 GMT
Opened by José Pedroso (josedpedroso) - Sunday, 23 January 2011, 21:32 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 26 January 2011, 14:07 GMT
|
DetailsDescription:
Saned is spamming syslog with messages like "Jan 23 21:16:56 localhost saned[1615]: run_standalone: accept failed: Socket operation on non-socket". I can scan from remote hosts just fine, but this is causing high load. A workaround is to kill the child saned process. This stops the messages and saned still works. The problem has been fixed in upstream, as per http://alioth.debian.org/tracker/index.php?func=detail&aid=312422&group_id=30186&atid=410366 Additional info: * package version: 1.0.21-4 i686 (might affect x86_64, but I couldn't test) * config file: saned exhibits this issue with both the default saned.conf and a modified one to allow hosts on my lan to scan Steps to reproduce: Run saned -a Check log file |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 26 January 2011, 14:07 GMT
Reason for closing: Not a bug
Wednesday, 26 January 2011, 14:07 GMT
Reason for closing: Not a bug
Comment by José Pedroso (josedpedroso) -
Wednesday, 26 January 2011, 13:56 GMT
Actually, saned works fine if started by xinetd (just found out that's how it's meant to be used from https://bugs.archlinux.org/task/22574), so this issue is moot.