I agree with the sentiment that we should work towards eliminating the dependency. In the meantime, until we figure out how to do that, it may be necessary for us to make changes to spot-nfdump. I would suggest that just for our own sanity, we should include/fork the project (open-network-insight/spot-nfdump) so we can make commits to it, and so that unknown people can't make changes that might affect our users. We could update the documentation to direct users to install our maintained version, instead of the external copy.
Jeremy On Wed, Feb 5, 2020 at 12:08 AM Nate Smith <[email protected]> wrote: > I’ve not been active in this project for a while, so forgive me if this > has already been addressed. > > I’m assuming this is for spot-nfdump? > > If so it’s worth saying unless someone has been maintaining it we should > look at removing the dependency. > > Originally we cooked our own version due to time stamp issues. But this > should really be handled post ingestion IMHO. > > - nathanael > > > On Feb 4, 2020, at 3:40 PM, skip cruse <[email protected]> wrote: > > > > I noticed when setting up nfdump for spot-ingest that there were some > > errors around the version of automake that’s requried. Apparently > automake > > 1.14 is required and after installing that everything worked fine. I did > > some digging and it looks like this was already raised via SPOT-178: > > https://issues.apache.org/jira/browse/SPOT-178. Perhaps someone could > > update the website to reflect this dependency and add the additional > setup > > steps in there as well? > > > > Cheers, > > Skip > > -- > > if( bool halfWayThere == true); > > printf "WOOOOOOOOOOOOOOOOAH! LIVIN ON A PRAYER"; >
