Module need Chownroot permission to init

[jsearby]

As module intialization depends on :
[module.go :: startMetricServer] err = os.Chown(socketPath, userID, groupID)
It cause following init error:
Cannot chown metricssocket: chown /tmp/mtr.0juus5: operation not permitted

When such module is run within a "secured" container it cannot pass the init state.
As long as we can configure the DEFAULTTMPFOLDER with proper permission upfront: => it could worth avoid to do this Chown.

(Thanks a lot in advance for any support you may provide, we are definitly lacking such module)

[sni]

The idea is to simply load the module and get metrics in return without worrying to much about preparation.
Is the apache started as uid=0 in your case? If not, the chown could be omitted, since the only reason is to create
a communication socket between the main process (which is mostly started as root) and the forked children running as
unprivileged user.

[jsearby]

Thanks for such reactivity !
I confirm my apache is not uid 0, it is running as a standard user.
I will do a try using a "local test version" of the module without the chown

[sni]

I would not remove the chown, but put it in a if and check for uid=0 before.

[jsearby]

Good new :
Using local recompiled module, I confirm that only the Chown issue was preventing the module to work on a non root (uid=0) apache. I've been doing some intensive testing and so far so good.
If ok with you I can try the PR you proposed ?
(unless you prefer to do it)

[sni]

sure, please prepare a PR and i am happy to merge it.