Barnyard2 is a replacement for the original Barnyard which is no longer maintained up stream. Barnyard2 is a tool to process Snort unified and unified2 logs and output alerts in various formats. Reproducible: Always The beginning of an ebuild for BY2 could be found at Bug #279019, however there were a number of issues with it. 1. I removed snort as a dependency since snort is not required to build or run BY2. Although, most users will run BY2 and snort on the same box, there are a number of deployment configurations where this is not the case. 2. I removed options for sguil because I do not use it, it was not tested in the previous ebuild, there were some errors with the sguil related stuff, and most people use mysql and BASE. 3. The ebuild at the above bug used "use_enable" for mysql, odbc, and postgres. This works, but causes an error during ./configure. I switched this back to "use_with" which works, produces no error, and is consistent with the snort ebuild. 4. Moved barnyard2.conf.distrb from /etc/snort to /etc/barnyard. This is a more appropriate location, especially when running multiple instances of BY2. 5. Fixed the problem of "/etc/init.d/barnyard2 stop" not working. This is related to how BY2 handles PID files. See the ebuild and barnyard.confd for more info. 6. Added post install info regarding configuration and listing what output plugins are considered stable up stream. 7. Created metadata.xml file for the ebuild I've been using this ebuild for a couple of months in production on x86 and amd64 boxes and have no issues to report. The repoman has been paid... # repoman full RepoMan scours the neighborhood... ebuild.allmasked 1 net-analyzer/barnyard2 Note: use --include-dev (-d) to check dependencies for 'dev' profiles RepoMan sez: "You're only giving me a partial QA payment? I'll take it this time, but I'm not happy."
Created attachment 222051 [details] barnyard2-1.7.ebuild
Created attachment 222053 [details] metadata.xml
Created attachment 222055 [details] barnyard2.confd Config file for /etc/conf.d
Created attachment 222057 [details] barnyard2.initd barnyard2 /etc/init.d/ script.
Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Thanks, On behalf of the Gentoo Sunrise Team, Justin. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
(In reply to comment #5) I'll contact you offline regarding this.
Version 1.8 was released for barnyard2. I'll upload the new ebuild, barnyard2.confd, and barnyard2.initd. There are no major functionality changes from 1.7 to 1.8. I made some minor modifications to the ebuild, barnyard2.confd, and barnyard2.initd to reflect an upstream bug fix and to clarify some of the variables in barnyard2.confd.
Created attachment 222675 [details] barnyard2-1.8.ebuild
Created attachment 222677 [details] barnyard2.confd
Created attachment 222679 [details] barnyard2.initd
Updated bug Summary from "net-analyzer/barnyard2-1.7 New Ebuild" to "net-analyzer/barnyard2-1.8 New Ebuild"
+ 16 Mar 2010; Patrick Lauer <patrick@gentoo.org> +files/barnyard2.confd, + +files/barnyard2.initd, +barnyard2-1.8.ebuild, +metadata.xml: + Initial import. Ebuild by Jason Wallace based on work by Fabio + Scaccabarozzi and Han Boetes . Closes #279019 and #307783
