bugzilla-daemon at netfilter.org
2014-Nov-23 11:18 UTC
[Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
https://bugzilla.netfilter.org/show_bug.cgi?id=977 --- Comment #28 from Eric Leblond <eric at regit.org> --- Hello, (In reply to Netbug from comment #27)> Hi Eric, >...> > So I thought you mentioned I need to have bind=1 uncommented? But it creates > these messags, so maybe there's still something going on here, and not a > user error at this point?Well that's message is just a warning message and it is not an error: "forcing unbind of existing log handler for protocol" It just says that ulogd will detach any other log handler to the protocol. So we display this message to warn user that could possibly use another log handler and discover that their other logging system is not working anymore. So this message is here to help them debug this potential issue. Maybe the current text is unclear, so suggestion welcome ;) -- You are receiving this mail because: You are watching all bug changes. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20141123/e460605d/attachment.html>
Reasonably Related Threads
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol