imegao/monitor_yig: main.go; 3 LoC

Found a possible issue in [imegao/monitor_yig](https://www.github.com/imegao/monitor_yig) at [main.go](https://github.com/imegao/monitor_yig/blob/b9240075436580f62a9ed1f4de6ef3847c4f287b/main.go#L33-L35)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

>

[Click here to see the code in its original context.](https://github.com/imegao/monitor_yig/blob/b9240075436580f62a9ed1f4de6ef3847c4f287b/main.go#L33-L35)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _,node:=range config.CONFIG.Process{
generateProcess(&node)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {generateProcess 1} was not found in the callgraph; reference was passed directly to third-party code
```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: b9240075436580f62a9ed1f4de6ef3847c4f287b

Review main.go lines 33-35 in the linked commit and the analyzer output about passing the range variable to generateProcess. Check the surrounding function context, then leave the reaction that best classifies the finding as Bug, Mitigated, or Desirable Behavior.

Written by the indexing model from the issue text.