Date: Wed, 21 Oct 2009 14:57:06 +0000 From: Paul Schmehl <pschmehl_lists@tx.rr.com> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Need advice from maintainers Message-ID: <D5F34484F338143BEE6437C3@utd65257.utdallas.edu>
next in thread | raw e-mail | index | archive | help
I am the maintainer for security/barnyard2. This is an updated version of security/barnyard, which I also maintain. The version of my port is the current release version, but it has a really irritating problem that is fixed in the current beta version. Barnyard2 is a program that parses snort logs and inserts them into a database (mysql or postgresql). It is supposed to create a placemarker file (called a waldo file) that maintains a record of what logs it has already parsed. (This is only one way of using the program. There are others as well.) The problem in the release version is that it does not read the waldo file when the program is restarted. So every time you restart barnyard2, it reinserts into the database every alert you still have log files for. The beta version fixes this problem. I have created a port for the beta version and am using it myself, but I know that using beta versions of software is frowned upon. Should I go ahead and submit this port because it solves this problem? If I do, my thinking is that I should adjust the pkg-message file in the existing port to warn the user about the problem and note that the beta version solves it so they might want to consider using that instead. Also, if I do submit the port, should it be named barnyard2-beta? Or barnyard2-devel? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D5F34484F338143BEE6437C3>