Fixed security issue with config file

[jkellerer]

This PR fixes a security issue with supervisord(is logged when used in latest Ubuntu releases).

Resolved problems:

• Prevent supervisord from searching for config files at standard paths by specifying the config to use.
• Create a complete config without unnecessary remote-control interfaces that are initialized when keeping the config from the distribution.
• Finally, tell supervisord that running as root is intended and no warning must be logged (after fixing the issues).

[Fmstrat]

@jkellerer I know it's been a while, but could you rebase against develop and resolve conflicts? Everything's been updated now to the latest ubuntu and samba.

[jkellerer]

@Fmstrat , rebase is done

[Fmstrat]

I'm not sure what security implication this has from reviewing it, but I do see you've replaced logs with stdout. If this is the case, which I'm good with, shouldn't line 182 and any other line like with tail change?

[jkellerer]

The security implications are listed in the description of the PR. It was about not specifying the config file in the call which means supervisor will search at default locations and use some files provided by the distribution. E.g. they enable remote control which is something not needed for this case.

Regarding log redirection, yes I agree, it should not be sent to a file at all. I can update this part.

[jkellerer]

@Fmstrat, log output should now only be stdout or err (no files). I had added env var LOGLEVEL to override defaults (or smb.conf).