Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian and RPM package feature request. #35

Open
vijaysar opened this issue Nov 5, 2017 · 0 comments
Open

Debian and RPM package feature request. #35

vijaysar opened this issue Nov 5, 2017 · 0 comments

Comments

@vijaysar
Copy link

vijaysar commented Nov 5, 2017

First of all for this good framework and nice software to get IPFIX data into big data like systems in a native and simple way. These are more feature requests I have to help see this in a production system at an ISP. My desire is to use these to create tools for DDOS early warning, malware detection like use cases. Here are the feature requests

  1. vflow_stress links to a file that is local or ssystem specific
  2. vflow running as a non root user.

1: vflow_stress problem
vflow_stress from rpm or debian seems to be linked to a GOPATH or package and cannot execute without a specific link to this file, see error below:

I can fake it to run but this will be a good one to fix.

vijay@linux: vflow_stress
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x78 pc=0x4a490e]

goroutine 4 [running]:
main.main.func1(0xc420010590, 0xc4200105a0, 0x10, 0x10)
/root/go/src/github.com/VerizonDigital/vflow/stress/stress.go:73 +0x7e
created by main.main
/root/go/src/github.com/VerizonDigital/vflow/stress/stress.go:80 +0xcc

2: vflow as a non-root user

The directories /usr/local/vflow and /var/log/vflow can all be owned by a user called "vflow" - in most systems that I manage we try to minimize things running as root, so it can be good to create a "vflow" user and chown the files and pid directories to be all with "vflow" user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant