Quoting Eric W. Biederman (ebiederm@xxxxxxxxxxxx): > > Since this still has not been addressed. I am going to repeat Andrews > objection again. > > Isn't there a better way to get iptables information out than to use > syslog. I did not have time to follow up on that but it did appear that Bruno suggested NFLOG target + ulogd. That's not ideal, but doable. At least each container should be able to do that for itself. What it won't do is let a host admin make sure that he doesn't get corrupted syslog entries when partial-lines get sent from several containers and the kernel and randomly spliced together. It also would simply be better if the information was *always* sent to userspace instead of syslog. > someone did have a better way to get the information out. > > Essentially the argument against this goes. The kernel logging facility > is really not a particularly good tool to be using for anything other > than kernel debugging information, and there appear to be no substantial > uses for a separate syslog that should not be done in other ways. > > That design objection must be addressed before merging this code can be > given serious consideration. > > Eric > _______________________________________________ > Containers mailing list > Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx > https://lists.linuxfoundation.org/mailman/listinfo/containers -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
