Closed Gent00157 closed 4 months ago
you probably need to enable external scripts in the module section. Aliases are set there.
Ahh, that's it! It works with CheckExternalScripts = enabled
, thank you for response and for snclient as well.
We have to enable CheckExternalScripts = enabled
to start aliases to work.
i probably gonna change that in the future to make alias work without enabling external scripts because that does not make sense to enable external scripts just for the aliases.
That would be nice, or at least get warning in the log file if CheckExternalScripts
is not enabled and aliases are used in config?
client certificates
in the server config, which is AFAIK not how the verification is commonly used (usually client cert is requested and then verified on the server against the CA [chain]).
I will let you know (PR) if I have some gotchas, but I am not crypto expert and have to learn golang basics first ;)
Thank you anyway for this project, really appreciatednext release would not have that external script requirement anymore: 411cb92a688b1a34c8e338d25865a59cef789f47
Hi, I am trying snclient as a replacement for (old) nscp on WIndows server 2012 and have an issue with alias commands.
alias_cpu
is defined in snclient.ini ( service restarted, no errors in snclient.log)[/settings/external scripts] timeout = 60 allow nasty characters = false allow arguments = false script root = ${scripts} script path = ignore perfdata = no
[/settings/external scripts/alias] alias_cpu = check_cpu "warn=load>90" "crit=load>95" ...