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

Test xml configuration and exit #64

Open
crossto opened this issue Mar 14, 2022 · 1 comment
Open

Test xml configuration and exit #64

crossto opened this issue Mar 14, 2022 · 1 comment

Comments

@crossto
Copy link

crossto commented Mar 14, 2022

Is there a way to validate xml configuration file other than ipfixcol2 -c <FILE>? I'm running timeout 1s ipfixcol2 -c <FILE> and catching RC 124 but that seems inelegant and prone to errors (slow read due to hdd spin up comes to mind).

@Lukas955
Copy link
Collaborator

Hi,

I took a quick peek at the code, but I couldn't think of a more elegant way. Unfortunately, this is not even easy to implement, because the part when plugins process their configuration is an integral part of their initialization, during which they perform other activities (e.g. creating sockets, etc.).

Therefore, even your proposed solution fails when the plugin that is part of the configuration needs to use some exclusive resource. For example, if you are running a collector that listens on TCP port 4739, and you want to test the new configuration with the same port at the same time, even the correct configuration will end up failing because the required port is already busy.

Lukas

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

2 participants